| commit | af677038b3d4703fde854b9c0723b63b1e2e0015 | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Wed May 17 16:18:25 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Mon May 22 09:57:48 2023 +0200 |
| tree | 91fa1bc4100bc7025e343dc495f71de21fb094fa | |
| parent | 07cfdab76a70abaaf9ae0d4260f2403415ddd5b5 [diff] |
aconfig: dump: support multiple caches Teach `aconfig dump` to read multiple caches at the same time. A cache represents a single namespace, and the Android build creates multiple caches for different namespaces. By passing in all those cache files to `aconfig dump`, aconfig will create a complete overview of all flags in the Android tree. Caches are traversed in order of namespace to produce the same output regardless of the order the cache files are given on the command line. If two caches use the same namespace, their order with respect to each other is undefined. Bug: 279485059 Test: atest aconfig.test Change-Id: I54c3950bbb7b2be7d96c8928e78ae83aa626c2e2
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.