| commit | 1c3d83b64cb856bc039f1bb2ade22e8583bcca3f | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu May 17 12:49:08 2018 -0700 |
| committer | Colin Cross <ccross@android.com> | Thu May 17 15:09:17 2018 -0700 |
| tree | 8322443c811eea731f46d9ce81a346172e57970e | |
| parent | 282065ab15b5c17ac4cb88760de38e4cb37ae192 [diff] |
Don't recompute location of AndroidManifest.xml The location of AndroidManifest.xml has already been computed by android_manifest.mk, don't duplicate the logic. Fixes an extra regeneration triggered by $(wildcard $(my_android_manifest)) when LOCAL_FULL_MANIFEST_FILE points to a generated file, which will not exist on the first run of kati. Test: m Change-Id: Ia56693a4dbbc7d78900019b887f766938dc55dab
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.