510b76d8ff
The majority of the contents in BoardConfig.mk of emulator products are the same. The common part is factored out as EmuConfig.mk so it's easier to maintain these closely related products going forward. Bug: 80117040 Test: Following products have been built and booted to homescreen: $ lunch aosp_x86-userdebug; m -j; emulator $ lunch aosp_x86_64-userdebug; m -j; emulator Change-Id: I5392e0e88865d4908906a67c29939c23af84baf0 |
||
|---|---|---|
| core | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Android.mk | ||
| buildspec.mk.default | ||
| Changes.md | ||
| CleanSpec.mk | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| OWNERS | ||
| README.md | ||
| tapasHelp.sh | ||
| Usage.txt | ||
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.