| commit | afc4604f6731f0d427dc48e3996d4ba3ffe9297b | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Tue Oct 30 13:21:07 2018 -0700 |
| committer | Colin Cross <ccross@android.com> | Tue Oct 30 15:48:25 2018 -0700 |
| tree | 323e675fc65478e4cdf63f6e7030093eea9d74cc | |
| parent | 0fb8c97b025afea23cff47f01fcc4a5ac0272a69 [diff] |
Create bundle modules suitable for bundletool Create a bundle module in addition to creating an APK, which can then optionally be merged with bundle modules from builds for other architectures and then be passed to bundletool to create an app bundle. Bug: 117295826 Test: tapas Gallery2 && m dist Change-Id: Ib9b5558888d6d6e841e8a5dcd7037dd0fd65a730
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.