| commit | e6b6c495d241bc4cb74f3ffa8f6bb75a34e9c208 | [log] [tgz] |
|---|---|---|
| author | Ricardo Cerqueira <ricardo@cyngn.com> | Mon Jan 25 16:49:27 2016 +0000 |
| committer | Jackeagle <jackeagle102@gmail.com> | Fri Aug 10 21:45:39 2018 -0400 |
| tree | d447fd124eb145876d7be51eee4efd4eff4316f2 | |
| parent | 8da71d11176c5f0ad8f07a64c1888b35230d808b [diff] |
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 binary: Don't run protobuf header relocations if origin/target are the same Change-Id: I3746746bdf1526674f345d884e2eccef85e946ef build: Fix LOCAL_PROTOC_OUTPUT * This code was refactored in 7.1 adjust accordingly. * This is used by projects like ril-caf where the proto-c generated sources dir might not match the project path. Change-Id: I7a7d0bb7a397b02deb5406a591059a877ac2c6da
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.