ef45381221
soong_ui is passing the Android.mk file list to Kati, and it ignores Android.mk files found via symlinks, so we don't need the workarounds for build/make/target/board/Android.mk and build/target/board/Android.mk both existing. We've got dist support in Soong now, so we can remove the signapk Android.mk Bug: 122332221 Test: m dist out/dist/signapk.jar out/dist/libconscrypt_openjdk_jni.so Change-Id: I2ac9016b04146340c5ac80f7090d00e186023574 |
||
|---|---|---|
| common | ||
| core | ||
| packaging | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Changes.md | ||
| CleanSpec.mk | ||
| OWNERS | ||
| README.md | ||
| Usage.txt | ||
| buildspec.mk.default | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| 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.