| commit | 73a34ce10a5e483ca17cb8a30d74c1510f50fab2 | [log] [tgz] |
|---|---|---|
| author | Zhi Dou <zhidou@google.com> | Wed Sep 13 19:55:50 2023 +0000 |
| committer | Zhi Dou <zhidou@google.com> | Thu Sep 14 13:00:45 2023 +0000 |
| tree | 85057eb8f91b4390bc54e1713bb8e2c8e74033f8 | |
| parent | 708dc5bf812eb5993f3118eeb81c6cb0e9f65b52 [diff] |
aconfig: throw exception if reading from DeviceConfig fails Reading value from DeviceConfig may fail if the provider is not ready. Since DeciceConfig, and Settings class are static wrapper on top of the provider, it won't cause the instance initialization issue. Thus when the issue happens it means the provider is not initialized. Test: atest aconfig.test.java and manually make a change in the framework and check the exception message Bug: 299471646 Change-Id: Ic08d7a9cd32a8810a7274b6d93c249abccb50b9e
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.