Ensure no mixing of device config and new storage flags in a package In a beta namespace, for a flag package, if the container is platform, then none of the flags should use device_config, if the container is mainline module, then none of the flags should use aconfigd. So there should not exist a case where we can have both device_config and aconfigd flags in a single flag package. This also simplifies codegen template, there is no mix of old and new in a single codegen template. Bug: b/406818480 Test: cd build/tools/aconfig/aconfig atest -c Change-Id: Ia2cd91b95dab9b69c9a512e3077b2eaade70fe10
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.