| commit | b0e1d2a3c4784e8d9874fcb97d46b96f7a5d0e7d | [log] [tgz] |
|---|---|---|
| author | Marybeth Fair <marybethfair@google.com> | Fri Mar 14 11:44:16 2025 -0400 |
| committer | Marybeth Fair <marybethfair@google.com> | Fri Mar 14 11:44:16 2025 -0400 |
| tree | db95a5e7790d81d4e96f3a0c6cce49a4d7ec59bf | |
| parent | b8503dbcc90835e1ba44b3d705ca427b338ffe06 [diff] |
aconfig: enforce all file versions are tested run the serialization tests (which enforces the round trip of into_bytes and from_bytes) for versions 1-MAX. ideally we won't have to support all versions forever, but until then we should make sure new versions are tested automatically Test: atest aconfig_storage_file.test Bug: 387282428 Change-Id: If0da10a64918148bc24257977f3fd337f4023f6c
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.