Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1146)

Unified Diff: build/protoc.gypi

Issue 9378041: Remove hand-rolled protobufs generation; enable rel paths in protoc.gypi (Closed) Base URL: http://git.chromium.org/chromium/src.git@master
Patch Set: removed hard_dependency Created 8 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | third_party/cacheinvalidation/cacheinvalidation.gyp » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: build/protoc.gypi
diff --git a/build/protoc.gypi b/build/protoc.gypi
index 555c5be45d29f3e0866eddc6aa996ec6a8a675ad..c48de3033fa0df2b4df22cf8b4550db66b844f67 100644
--- a/build/protoc.gypi
+++ b/build/protoc.gypi
@@ -32,8 +32,24 @@
# like:
# #include "dir/for/my_proto_lib/foo.pb.h"
#
+# The 'proto_relpath' variable specifies another way to provide the path
+# suffix that files are generated under. 'proto_relpath' exists because there
+# are some protos which import using qualified paths, rather than the more
+# common relative import.
+#
+# By using 'proto_relpath', projects can continue to use qualified imports
+# instead of enforcing an import style through this gypi. If provided,
+# 'proto_relpath' must have a trailing slash.
+#
# Implementation notes:
-# A proto_out_dir of foo/bar produces
+# A 'proto_out_dir' of 'foo/bar', with no 'proto_relpath' provided, produces:
+# <(SHARED_INTERMEDIATE_DIR)/protoc_out/foo/bar/{file1,file2}.pb.{cc,h}
+# <(SHARED_INTERMEDIATE_DIR)/pyproto/foo/bar/{file1,file2}_pb2.py
+#
+# By setting 'proto_relpath' to 'foo/bar', with a 'proto_out_dir' of '', the
+# protos can use qualified imports instead of relative imports,
+# e.g. #import "foo/bar/file2.proto"; instead of #import "file2.proto";
+# A 'proto_out_dir' of '', with a 'proto_relpath' of 'foo/bar/' produces:
# <(SHARED_INTERMEDIATE_DIR)/protoc_out/foo/bar/{file1,file2}.pb.{cc,h}
# <(SHARED_INTERMEDIATE_DIR)/pyproto/foo/bar/{file1,file2}_pb2.py
@@ -43,6 +59,7 @@
'cc_dir': '<(SHARED_INTERMEDIATE_DIR)/protoc_out/<(proto_out_dir)',
'py_dir': '<(PRODUCT_DIR)/pyproto/<(proto_out_dir)',
'proto_in_dir%': '.',
+ 'proto_relpath%': '',
},
'rules': [
{
@@ -52,16 +69,16 @@
'<(protoc)',
],
'outputs': [
- '<(py_dir)/<(RULE_INPUT_ROOT)_pb2.py',
- '<(cc_dir)/<(RULE_INPUT_ROOT).pb.cc',
- '<(cc_dir)/<(RULE_INPUT_ROOT).pb.h',
+ '<(py_dir)/<(proto_relpath)<(RULE_INPUT_ROOT)_pb2.py',
+ '<(cc_dir)/<(proto_relpath)<(RULE_INPUT_ROOT).pb.cc',
+ '<(cc_dir)/<(proto_relpath)<(RULE_INPUT_ROOT).pb.h',
],
'action': [
'<(protoc)',
'--proto_path=<(proto_in_dir)',
# Naively you'd use <(RULE_INPUT_PATH) here, but protoc requires
# --proto_path is a strict prefix of the path given as an argument.
- '<(proto_in_dir)/<(RULE_INPUT_ROOT)<(RULE_INPUT_EXT)',
+ '<(proto_in_dir)/<(proto_relpath)<(RULE_INPUT_ROOT)<(RULE_INPUT_EXT)',
'--cpp_out=<(cc_dir)',
'--python_out=<(py_dir)',
],
« no previous file with comments | « no previous file | third_party/cacheinvalidation/cacheinvalidation.gyp » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698