| commit | da04a3d44d73abca3f52fbc52d6a0cf8124e06b8 | [log] [tgz] |
|---|---|---|
| author | Justin Yun <justinyun@google.com> | Tue Jan 07 14:36:42 2025 +0900 |
| committer | Justin Yun <justinyun@google.com> | Fri Feb 07 15:26:13 2025 +0900 |
| tree | 5e838d6a15cc56d722fc3c608ebd6cf3129437c8 | |
| parent | d4c9347422a7ed18175b6004196006ae1fdae4d3 [diff] |
Create aconfig_flags for all containers. Some targets do not create images for some non-system partitions, but include them in the system partition. Even in such cases, create the aconfig_flags in the etc directory of the original container. For example, system_ext aconfig_flags.pb can be installed in system/system_ext/etc/aconfig_flags.pb. With this change, add system_ext to the aconfig paths along with the other partitions. Bug: 385213580 Test: lunch gsi_x86_64_soong_system-trunk_staging-userdebug && m Change-Id: I660eb2e3d55850680ca610b8b756495d1769de4c
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.