Write fingerprint to package map.

Write fingerprint to package.map fingerprint field. This involves some
re-work of how the fingerprint is calculated. Guard the write with a
new arg in create-storage, enable-fingerprint. The default value for
enable-fingerprint is false, and I haven't updated the build code to
pass in anything, so none of this code should run right now. Next step
is to create a build flag and use that to set enable-fingerprint so we
can roll out this change. Then, I will use the fingerprint in codegen as
well.

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