Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / cccf2ca33706e0582465f385aae14d6d8a242b5b
commitcccf2ca33706e0582465f385aae14d6d8a242b5b[log] [tgz]
authorJoe Onorato <joeo@google.com>Wed Sep 28 22:52:56 2022 -0700
committerJoe Onorato <joeo@google.com>Wed Sep 28 23:46:18 2022 -0700
treea55ae1241dde6173e57cb802c27100e404752062
parentc2b7a831903d8e8bc10b7ce617bb9167267e921b [diff]
Add a tool that will tell which git projects are used for a build target

See build/make/tools/whichgit -h for the options

Test: build/make/tools/whichgit --modules com.google.android.tzdata
Test: build/make/tools/whichgit --modules framework
Test: TARGET_BUILD_APPS=com.google.android.tzdata4 build/make/tools/whichgit --products mainline_modules_arm64 --variants eng --modules $TARGET_BUILD_APPS --why "*"
Change-Id: I05d91b85575a920b3ec9f5959e2ce463a45e63a3
1 file changed
tree: a55ae1241dde6173e57cb802c27100e404752062
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. finalize-aidl-vndk-sdk-resources.sh
  15. finalize-step-1.sh
  16. finalize_branch_for_release.sh
  17. help.sh
  18. METADATA
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. tapasHelp.sh
  25. 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.