b894d4bb68
Contents that were in /vendor/default.prop are now in /vendor/build.prop The content is placed at the top of build.prop to keep the existing order between default.prop and builld.prop. Bug: 117892318 Test: TH passes Test: inspect /vendor/build.prop and check if it has contents from the old /vendor/default.prop file Change-Id: Ifa1f1dca3b4f4a5fa87d26b8ee058ee706dc54bb |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
OWNERS | ||
README.md | ||
Usage.txt | ||
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.