Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 7cdfd674d5d7452eb9654140e4c2f1680f7e7acc
commit7cdfd674d5d7452eb9654140e4c2f1680f7e7acc[log] [tgz]
authorbohu <bohu@google.com>Thu Jun 07 09:19:19 2018 -0700
committerbohu <bohu@google.com>Thu Jun 07 09:19:19 2018 -0700
tree6c448994c1027fa4826d457352145bf3f01e2671
parentef449b9250baa0f186165cc76dc37c5738609696 [diff]
emulator: allows vendor_init to set qemu_props

BUG: 109872686

this cl only impacts emulator images

Change-Id: I93b8489f710d194917d4b482ebca960c39658fd9
1 file changed
tree: 6c448994c1027fa4826d457352145bf3f01e2671
  1. core/
  2. target/
  3. tests/
  4. tools/
  5. .gitignore
  6. Android.mk
  7. buildspec.mk.default
  8. Changes.md
  9. CleanSpec.mk
  10. envsetup.sh
  11. help.sh
  12. navbar.md
  13. OWNERS
  14. README.md
  15. tapasHelp.sh
  16. Usage.txt
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.