Google Git
Sign in
android/platform/build/0ab9187f01
commit
0ab9187f015f7c2c627dedc341a1c3a7e3f72dbf
[log]
author
Ayush Sharma <ayushsha@google.com>
Wed Dec 22 11:56:11 2021 +0000
committer
Ayush Sharma <ayushsha@google.com>
Wed Dec 22 11:56:11 2021 +0000
tree
db55028c5fdd61c2d3fe045e3c30df94d38fb579
parent
5d2cf578d6b64e03d0babac436dfbbb4f9886971 [diff]
Revert "Removing gsi_keys.mk"

This reverts commit 5d2cf578d6b64e03d0babac436dfbbb4f9886971.

Reason for revert: DroidMonitor-triggered revert due to breakage https://android-build.googleplex.com/builds/quarterdeck?branch=git_sc-qpr1-dev-plus-aosp&target=build_test3&lkgb=8021524&lkbb=8021634&fkbb=8021569, bug https://buganizer.corp.google.com/issues/211737534

Bug: 211737534
Change-Id: I40e8dce5d87a1ba08a6f100fc2af92dd94fd2d5c
1 file changed
tree: db55028c5fdd61c2d3fe045e3c30df94d38fb579
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. Android.bp
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. Deprecation.md
  14. envsetup.sh
  15. help.sh
  16. METADATA
  17. navbar.md
  18. OWNERS
  19. PREUPLOAD.cfg
  20. rbesetup.sh
  21. README.md
  22. tapasHelp.sh
  23. 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.