commit | df7efa62422b6d9d2e849361a4964d28dc67b68c | [log] [tgz] |
---|---|---|
author | Spandan Das <spandandas@google.com> | Fri Nov 01 18:21:56 2024 +0000 |
committer | Spandan Das <spandandas@google.com> | Fri Nov 01 18:26:24 2024 +0000 |
tree | 272a664321246974f52d34ec365c0f12a5691bc5 | |
parent | 6c68c5a3d4b1c61c6ec53def888c4fec870199ce [diff] |
Explicitly declare selinux_policy_(vendor|odm) in PRODUCT_PACKAGES As part of the mk->bp migration, we are currently using heuristics to classify the packages in `PRODUCT_PACKAGES` to deps of the different android_filesystem modules. To aid such heuristics, separate phony targets will be created for selinux_policy_vendor and selinux_policy_odm. The former wil be added to deps of the autogenerated vendor module and the latter will be added to deps of the autogenerated odm module Bug: 376755916 Test: Verified that NOTICE.xml.gz is the only diff in fileList contents between kati and soong odm.img Change-Id: I001080011e9a89b8053e91b042ed82e215b0187e
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.