Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 7f00905643b8571f064794b7e9a80f264b6df04a
commit7f00905643b8571f064794b7e9a80f264b6df04a[log] [tgz]
authorJack Yu <jackcwyu@google.com>Tue Dec 17 16:10:16 2019 +0800
committerJack Yu <jackcwyu@google.com>Tue Dec 17 09:25:50 2019 +0000
tree0a1709735d071af94666e49101a75b8b6d2d3aac
parent2f4a8bb534057a3a2ac50aac1f55d50e52c08692 [diff]
Add android.hardware.secure_element@1.2

Test: build pass
Bug: 142495673
Change-Id: I26e63a960afa721454aee9000d57655068b11a7f
1 file changed
tree: 0a1709735d071af94666e49101a75b8b6d2d3aac
  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.