| commit | 2e47c7bbd3e29572fa075923becf9f5d14f3aeb1 | [log] [tgz] |
|---|---|---|
| author | LaMont Jones <lamontjones@google.com> | Fri Jan 26 18:23:47 2024 +0000 |
| committer | LaMont Jones <lamontjones@google.com> | Tue Jan 30 19:15:28 2024 +0000 |
| tree | 48aedaaaa8dfb26d45176c137c6219a55f6a86fd | |
| parent | 4767d785c1297043426507e9f39077f3398442d4 [diff] |
Add device_aconfig_declarations target Building device_aconfig_declarations creates simplifies listing all aconfig flags used on the device by creating a build artifact at: $(OUT_DIR)/target/product/$(TARGET_PRODUCT)/device_aconfig_declarations.pb Bug: b/308625757 Test: manual Change-Id: Ic5eef9c6a26f7893b3f4bdfed2cd4ac82a54a8f9
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.