0e4a5ad24b
When rule action contains something like cp $(FOO) ... and FOO is set with FOO := a \ b \ the generated Ninja file constains extra spaces, making it difficult to compare it to the same file generated by the Starlark-based product configuration. Bug: 181797530 Test: manual Change-Id: I278bd8edf0f017a31c5b5115b2a38f4f663c55fc |
||
|---|---|---|
| common | ||
| core | ||
| packaging | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Android.bp | ||
| Changes.md | ||
| CleanSpec.mk | ||
| Deprecation.md | ||
| METADATA | ||
| OWNERS | ||
| PREUPLOAD.cfg | ||
| README.md | ||
| Usage.txt | ||
| banchanHelp.sh | ||
| buildspec.mk.default | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| rbesetup.sh | ||
| tapasHelp.sh | ||
README.md
Android Make Build System
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.