| commit | 559047858042e05187085f12d9eadcc2c4e6b5e9 | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Wed May 22 13:57:43 2024 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Wed May 22 19:25:17 2024 +0000 |
| tree | 1ea731db85d50149e2f7372b1caabb0a170dbfbf | |
| parent | 22135a0b0c25ffe3224eb5e09b9f818b97a62b9e [diff] |
aconfig: update storage read api Update storage read api to not find storage file location from a pb file, instead directly read from /metadata copy. Previously for package.map and flag.map, we are reading from the respective RO partition. Now we are reading from /metadata/maps dir. This has a few advantages: 1, early flag availability, since /metadata can be mounted much earlier than mainline modules, so it would make mainline flags availabile even before mainline modules are mounted. 2, we no longer need to read from a pb file to find where package.map and flag.map are. Thus the read api can be further simplified and downsized. With this change, we are able to shrink the cc flag read api lib size from 171k to 120k. Bug: b/321077378 Test atest -c Change-Id: Ic9086fe4c49c139a4d1c66a8d472023a88c9dd17
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.