Update test mode codegen for nextfood

There is a cc test mode codegen lib that failed to build when enabling
read from new storage. The underlying issue is that in nextfood, all
flags are RO, even the fallback should just return a hardcoded value.
Before this change, it still tries to read from storage file which
caused a build failure.

Test: m
Bug: b/370046610
Ignore-AOSP-First: need to go with a git_main only change, will CP it back to aosp afterwards.
Change-Id: I4267ac9eb1fc6b068a8808e76d698a12936e31b6
1 file changed
tree: 18565fc237a3c2a15df5fc92d9e03957df924bbd
  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.