Google Git
Sign in
android / platform / build / ea2cd73c1f
commitea2cd73c1f4a4e9680fee256ed884a6e84223dd8[log] [tgz]
authorAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Tue Feb 15 03:12:54 2022 +0000
committerAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Tue Feb 15 03:12:54 2022 +0000
tree253935075394955414419d0e93233e67e516a819
parented143227a1c43f7a16f434b6d91590d9f503b240 [diff]
Version bump to TD1A.220215.002 [core/build_id.mk]

Change-Id: I6778f62c3d90dbf59bf4f3e7c2696dcdfb6d27f5
1 file changed
tree: 253935075394955414419d0e93233e67e516a819
  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. help.sh
  15. METADATA
  16. navbar.md
  17. OWNERS
  18. PREUPLOAD.cfg
  19. rbesetup.sh
  20. README.md
  21. tapasHelp.sh
  22. 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.