Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / 76670ce735160a23fd4291d670b4d84ccac915b3
commit76670ce735160a23fd4291d670b4d84ccac915b3[log] [tgz]
authorTreehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com>Thu Feb 29 04:37:59 2024 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Thu Feb 29 04:37:59 2024 +0000
tree854b65cac5e861f4e57aa5e77e7727b135074c10
parentfe06f890cd65021c4cc79ff24caffa49948c350a [diff]
parentbe9415326616d0d87293f286c23d20d77e4d58fa [diff]
Merge "Define PRODUCT_SHIPPING_VENDOR_API_LEVEL" into main am: be94153266

Original change: https://android-review.googlesource.com/c/platform/build/+/2980493

Change-Id: I1d3c2de54819a56dda023489a27920e9c87a1528
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 854b65cac5e861f4e57aa5e77e7727b135074c10
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. banchanHelp.sh
  11. buildspec.mk.default
  12. Changes.md
  13. CleanSpec.mk
  14. cogsetup.sh
  15. Deprecation.md
  16. envsetup.sh
  17. help.sh
  18. METADATA
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. 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.