| commit | e520633e6c2611f54091091acb69e1d81cca0cba | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Tue Nov 06 09:04:13 2018 -0800 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Nov 06 09:04:13 2018 -0800 |
| tree | 0d37ea02b3b0db1b0b9a2dc9a574b7dad77aea8e | |
| parent | 91794ed07e73d3d3b7a0993b19044d95174cfecf [diff] | |
| parent | bcbea5355fd9b650e3a2510bad9462643eb21b69 [diff] |
Merge "Only zip2zip bundle resources if they exist" am: 6a806e76d4 am: 6053f39b6c am: bcbea5355f Change-Id: If25fe3286b1637d2f31d9c5bfb4a4dc04efa4768
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.