| commit | d555bbfa80159e9168d1fd0e5dd7d042ee59dc3b | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Fri Dec 15 20:33:37 2023 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Mon Dec 18 13:43:22 2023 +0000 |
| tree | 12e02e0b2e2cfdbc3e9c2c5c169fca347a0bf0a2 | |
| parent | 1a03031a99f738f61a33e3f03ac9d91b6d5e9eab [diff] |
aconfig: update c/c++ codegen 1, Current codegen would still include an empty flag value cache even if there are no read write flags. This is important as the flag value cache is a std::vector. Thus adding this cache would automatically pull in libc++ dependency which we should not. 2, There lacks of c/c++ codegen unit tests to lock down the generated code when a flag package contains only read only flags. It should not include server_configurable_flags header. And it should not include the flag cache. Bug: b/316614694 Test: atest aconfig.test Change-Id: Iee4366672932ee507694f5fc73b526c66fcf0e9b
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.