| commit | 58472e8609b153824b4920f098ae908bc4b5cd6c | [log] [tgz] |
|---|---|---|
| author | Martin Stjernholm <mast@google.com> | Fri Jan 07 22:08:47 2022 +0000 |
| committer | Martin Stjernholm <mast@google.com> | Fri Jan 07 23:08:53 2022 +0000 |
| tree | 81d7118cefeab1412b7121926fc48e8b9a66dc6b | |
| parent | 8c861cec97383a30eaef1ea4f68b2ed04f41f5b8 [diff] |
Add an option to specify the path to aapt2. Thin manifests (e.g. master-art) may not have the aapt2 sources and instead relies on the prebuilt in prebuilts/sdk/tools/linux/bin. In that case there's no aapt2 in the search path, so it needs to be specified. Test: Heavy presubmit build on mainline_modules_bundles on git_master Test: vendor/google/modules/ArtGoogle/build-art-module.sh with http://ag/16584845 on git_master-art, where only the prebuilt aapt2 is present Bug: 212462945 Change-Id: I41a22e8146f5a88534c2721345b4d9d64f76698c
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.