| commit | b8205595c078fe317530100a6c276c415332bec5 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Fri Jun 07 13:36:17 2019 +0100 |
| committer | Yo Chiang <yochiang@google.com> | Fri Oct 04 20:25:14 2019 +0800 |
| tree | 968af6a06d38188b85e4236a4911aeb30bf3ebac | |
| parent | f89f29d669387d0376b0594b0ee1a1447cd09906 [diff] |
Re-submit "Make mainline device use apex" The build system default was changed to not support apex, but we want the mainline device to enable it. Test: make mainline_system Merged-In: I9f29e8354acffb1856dfd8a173b80a3f9324630c Change-Id: I9f29e8354acffb1856dfd8a173b80a3f9324630c
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.