Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 8e2b776def4c0837622182b106787655cdbd0d6e
commit8e2b776def4c0837622182b106787655cdbd0d6e[log] [tgz]
authorShawn Willden <swillden@google.com>Fri Oct 18 11:17:57 2019 -0600
committerShawn Willden <swillden@google.com>Wed Nov 20 12:14:36 2019 -0700
treecc4d2fa494c706db0e5c8a5ee5da031d005c6c8b
parente6c1e50be8939ef2bf0164002ffac15a68709f26 [diff]
Add Keymaster 4.1

Bug: 140193672
Bug: 140192237
Bug: 140824829
Test: Will be in a future CL
Change-Id: I1dccdf1ba06dc834e31d20c782523c92666847be
1 file changed
tree: cc4d2fa494c706db0e5c8a5ee5da031d005c6c8b
  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. README.md
  17. tapasHelp.sh
  18. 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.