commit | 5aaeee37495f3532198cca1679b85ba44cbf6bb6 | [log] [tgz] |
---|---|---|
author | Zhi Dou <zhidou@google.com> | Mon Aug 07 22:54:13 2023 +0000 |
committer | Zhi Dou <zhidou@google.com> | Tue Aug 08 20:35:18 2023 +0000 |
tree | 49776a2e05e8cba55bd1f0549ed41f6e3db1c72f | |
parent | 1afb7ffec29d9edcaf9ef565c84a390a6142fed0 [diff] |
Generate FakeFeatureFlagsImpl in test mode Before FeatureFlagsImpl will be used as a fake for testing. This change adds new class FakeFeatureFlagsImpl. The FeatureFlagsImpl will keep the same as production. FakeFeatureFlagsImpl can be used as fake for testing. FakeFeatureFlagsImpl, and FeatureFlagsImpl will be generated in both test and prod mode. In test mode FeatureFlagsImpl will just be a stub, and in prod mode FakeFeatureFlagsImpl will just be a stub. Bug: 280833463 Test: atest aconfig.test Change-Id: I11c1e716a9ea00d55600e5e9d5fb6442420762e6
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.