Support mainline beta production mode codegen

Mainline beta production mode codegen will use device config as storage
backend. Also, the starting implementation will not cache flag values in
the codegen. This is more in line with legacy flags. Mainline developers
have the best flexibity this way. In some use cases, the flag values are
cached in the code. In some cases (like flag read each time wifi turns
on), flag value are not cached and always read from storage.

Bug: b/406508083
Test: m and added unit test point
Change-Id: I201cb886cf972a71b61c7bb0428c675028db13b0
2 files changed
tree: 80852bb14ab6774fde8bdeb1bd8a511863b43d92
  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.