diff options
author | Ricardo Cerqueira <ricardo@cyngn.com> | 2016-01-25 16:49:27 +0000 |
---|---|---|
committer | Ricardo Cerqueira <ricardo@cyngn.com> | 2016-01-26 00:17:52 +0000 |
commit | 947c4cdf1c7653b7aacafca38955234a5a33f364 (patch) | |
tree | f18b1f164a0f5790b44890e9b9af61aea434a478 /core/clear_vars.mk | |
parent | 9be9dd173eb69ac581a78f619b90d027095446d4 (diff) | |
download | build-947c4cdf1c7653b7aacafca38955234a5a33f364.zip build-947c4cdf1c7653b7aacafca38955234a5a33f364.tar.gz build-947c4cdf1c7653b7aacafca38955234a5a33f364.tar.bz2 |
binary: Allow specifying a path for generated proto headers
protobuf compilation defaults to dropping the generated objects and
headers onto a path derived from the origin source path. This poses
a problem with some of our repositories since they're not placed in
their original paths, and may include hard references to pb headers
assuming the original directory.
Typical use of this will be to place a
LOCAL_PROTOC_OUTPUT := <original repo path>
line in the relevant module block (for example, "hardware/ril" for our
"hardware/ril-caf")
Change-Id: Ib9b0cadd47e29a0d2e693b331cfc18e71b048ee5
Diffstat (limited to 'core/clear_vars.mk')
-rw-r--r-- | core/clear_vars.mk | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/core/clear_vars.mk b/core/clear_vars.mk index 794e1a9..5c53c9f 100644 --- a/core/clear_vars.mk +++ b/core/clear_vars.mk @@ -293,6 +293,8 @@ LOCAL_MODULE_STEM_64:= LOCAL_CLANG_32:= LOCAL_CLANG_64:= +LOCAL_PROTOC_OUTPUT:= + # Include any vendor specific clear_vars.mk file -include $(TOPDIR)vendor/*/build/core/clear_vars.mk |