commit | eabe74325e94b2fa23a1a723f58b3905bb880e8f | [log] [tgz] |
---|---|---|
author | Jihoon Kang <jihoonkang@google.com> | Tue Dec 10 01:34:59 2024 +0000 |
committer | Jihoon Kang <jihoonkang@google.com> | Tue Dec 10 01:34:59 2024 +0000 |
tree | 4602ff3953738e91b8489e0a034a0aa69094b266 | |
parent | 713daec03aa058fd56c521af253952fe482d9c1a [diff] |
Do not install Android.bp file in recovery partition https://r.android.com/3390999 accidentally led to the Android.bp file being installed in the recovery partition. This change modifies the make logic to ensure that the make generated recovery partition does not install the Android.bp file. Test: aninja -t query out/target/product/vsoc_x86_64/obj/PACKAGING/recovery_intermediates/ramdisk_files-timestamp && verify Android.bp is not included Bug: 381888358 Change-Id: I29e74b6816cbec7cc44c7a9cc4a9330f7f4c4018
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.