| commit | bfc7811441b83dc7b8bf6621c9e3e246e4d4c114 | [log] [tgz] |
|---|---|---|
| author | Joe Onorato <joeo@google.com> | Sat Oct 07 23:44:05 2017 -0400 |
| committer | Joe Onorato <joeo@google.com> | Fri Dec 15 08:40:48 2017 -0800 |
| tree | 164d672234577e67623e8bcbe3ca23263ec5760d | |
| parent | adcd4c761d7c89b978cc8fdb22011ae65e9feb0a [diff] |
When compiling with the lite protobuf option, pass the option to aprotoc to force the lite runtime. With LOCAL_PROTO_OPTIMIZE_TYPE set to one of the lite variants, the build system thinks the proto should be compiled with lite, and will link in the line runtime libs. But if the .proto files don't contain the directive to compile the source as lite (option optimize_for = LITE_RUNTIME;), then the generated code will be full and the libraries will be full, and it won't link. Test: make Merged-In: Ib8a135218d62fa42fa6448c49c97f7aeb2755c42 Change-Id: Ib8a135218d62fa42fa6448c49c97f7aeb2755c42
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.