| commit | 93293cd27a1f95d25f15072679a30ab63ff5b791 | [log] [tgz] |
|---|---|---|
| author | Yo Chiang <yochiang@google.com> | Fri Oct 04 21:28:42 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Fri Oct 04 21:28:42 2019 -0700 |
| tree | 4cdd5cc623f93a1ec66b2e473a63e8c50a788704 | |
| parent | eb40fdcf7e2d8e76e48a833ebe04c8b11450e011 [diff] | |
| parent | bf13035f050a768acb64170a354a68031ecbc721 [diff] |
[automerger skipped] Merge "Re-submit "Make mainline device use apex"" am: 491966fb7f am: db7529d009 am: a3be8add34 am: bf13035f05 -s ours am skip reason: change_id I9f29e8354acffb1856dfd8a173b80a3f9324630c with SHA1 e08363da37 is in history Change-Id: I68bfc42e65eca343fd975f39d6c671678d43d8fe
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.