Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / eadde46c4e5deffd432c7ce855d6ca383fda67dd
commiteadde46c4e5deffd432c7ce855d6ca383fda67dd[log] [tgz]
authorMarybeth Fair <marybethfair@google.com>Thu Dec 12 14:44:34 2024 -0500
committerMarybeth Fair <marybethfair@google.com>Tue Dec 17 08:13:14 2024 -0800
treeb83bbc1765402932dd255b877eeb74b0ef2cf2e2
parented045d3050d09d5eb4d186ded3e868e61f5018a6 [diff]
Connect fingerprint build flag to v2.

If RELEASE_FINGERPRINT_ACONFIG_PACKAGE is enabled, the storage file
version arg supplied to aconfig create-storage will be v2. Otherwise,
send v1 (current default).

As the build flag is not enabled, this change should be a no-op.
Confirmed by building that the files were still v1.

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