45b0438cc0
I was updating the format of PackageTableHeader to add an additional field (and due to that change incremented the file version). This broke several tests under aconfig_storage_read_api and aconfig_storage_write_api that were operating on files written in the old schema. I tried to re-generate them using aconfig create-storage as explained in aosp/2933375, but was having some trouble. Figure if we can just update the files directly it will be easier to make updates in the future anyway. This isn't bypassing logic that's tested - IIUC the tests cover reading the file correctly (writing is covered in separate tests). Usage: $ aconfig-storage print --file=path/to/flag.map --type=flag_map --format=json > flag_map.json $ vim flag_map.json // Manually make updates $ aconfig-storage write-bytes --input-file=flag_map.json --output-file=path/to/flag.map --type=flag_map Change-Id: I212bf0b97483740b30130eb121acb895d350da84 Test: manual (adding debug-only tooling) + cargo t Bug: 316357686
Android Make Build System
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.