Google Git
Sign in
android / platform / build / d313b1897f
commitd313b1897fb30437da75378d6ec6bbce7ebeb48b[log] [tgz]
authorOriol Prieto Gascó <opg@google.com>Mon Jun 16 07:49:58 2025 -0700
committerOriol Prieto Gascó <opg@google.com>Mon Jun 16 08:06:43 2025 -0700
treedf6c4b579dcf621496814e68e3b528ee95d4b99b
parentf0148d0ba107841b946534530a448d25e0a75137 [diff]
Suppress error logging when storage file is not available on host

The files that store flag value overrides on Android devices are absent
from host devices. As a result, the default values are always returned
when running on the host. This change prevents error messages caused by
the absence of storage files when running on the host.

Bug: 419824590

Test: atest aconfig.test

Flag: EXEMPT host code

Change-Id: I4e6185284e0726846c5cf36ac036d18fd1d51262
2 files changed
tree: df6c4b579dcf621496814e68e3b528ee95d4b99b
  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.