Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 91a7e3194b808489506aedebcce72463e51d0400
commit91a7e3194b808489506aedebcce72463e51d0400[log] [tgz]
authorHridya Valsaraju <hridya@google.com>Thu Aug 09 11:10:05 2018 -0700
committerHridya Valsaraju <hridya@google.com>Mon Aug 13 10:16:27 2018 -0700
tree42f2e476adebe97d839b0c0f6200b4d58654f04e
parente318a785495e1557f042c62a5878a496174c6520 [diff]
Add fastbootd to build targets

Bug: 78793464
Test: mmm
Change-Id: I0f7101d2ef948c522f8e4cfd51b91d33b59e1866
2 files changed
tree: 42f2e476adebe97d839b0c0f6200b4d58654f04e
  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.