Google Git
Sign in
android / platform / build / 5212d870ea
commit5212d870ea15c0cfb7e41f676cdc9f03ef7b38e6[log] [tgz]
authorandroid-build-team Robot <android-build-team-robot@google.com>Sat Jan 09 02:42:37 2021 +0000
committerandroid-build-team Robot <android-build-team-robot@google.com>Sat Jan 09 02:42:40 2021 +0000
tree05e61cad02e7fb7e5478a6d1856a62c781eb449f
parente090740b1ba4aa41cd7d1cf65a2c86634df4f165 [diff]
Version bump to SD1A.210109.002 [core/build_id.mk]

Change-Id: I5e64b760607e63400b65f0909b7b505e5f1c3edf
1 file changed
tree: 05e61cad02e7fb7e5478a6d1856a62c781eb449f
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. buildspec.mk.default
  9. Changes.md
  10. CleanSpec.mk
  11. Deprecation.md
  12. envsetup.sh
  13. help.sh
  14. navbar.md
  15. OWNERS
  16. rbesetup.sh
  17. README.md
  18. tapasHelp.sh
  19. 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.