Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 2f7a108bf21692ec4052c2350c4be9fc322b2eff
commit2f7a108bf21692ec4052c2350c4be9fc322b2eff[log] [tgz]
authorYi-Yo Chiang <yochiang@google.com>Tue Feb 22 19:13:32 2022 +0800
committerYi-Yo Chiang <yochiang@google.com>Thu Feb 24 21:47:51 2022 +0800
tree4f9a6ca1fed40a76c1fece722b022d724d668eee
parent0835ac67b6c33f5166f686641160a1ae25bca303 [diff]
Update T GKI certification scheme

* Remove 'generic_ramdisk' certification, as we are not certifying
  'init_boot' anymore.
* Add a new 'boot' certificate that certifies the whole boot.img.
* The new 'boot' & existing 'generic_kernel' certificates are directly
  appended at the end of the boot.img, and the mkbootimg
  --boot_signature argument is removed.

Bug: 211741246
Test: m bootimage
Test: ./boot_signature_info.sh boot-5.10.img
Change-Id: I143680b1cab50a6915df56c8273f8741beaf1180
1 file changed
tree: 4f9a6ca1fed40a76c1fece722b022d724d668eee
  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.