| commit | fc74734795b60ef1bc732919abeae2f358e2d8a2 | [log] [tgz] |
|---|---|---|
| author | Michael Bestas <mkbestas@lineageos.org> | Wed Mar 12 05:26:49 2025 +0200 |
| committer | Luca Stefani <luca.stefani.ge1@gmail.com> | Wed Mar 12 18:37:12 2025 +0100 |
| tree | 786d32231ad23f527896198dc021c1b5ec9cc50d | |
| parent | 3cbc8e7c455c0d9a73e81e1271ef9dbb2e477e82 [diff] |
Revert "Always include vendor_manifest.xml in PRODUCT_PACKAGES" This reverts commit 239c5308eb03ac8490ce4e66b62ad9fec3999874. Reason for revert: This breaks targets that use _only_ DEVICE_MANIFEST_SKUS and DEVICE_MANIFEST_<SKU>_FILES, since vendor_manifest.xml is non existent on those targets. The original change assumed it would be possible to add an entry to PRODUCT_PACKAGES even if not existing, but that's not the case. In the soong-only case this may work as we'd simply skip the module installation via m.SkipInstall(), but when generating Android.mk, as vintf_data does, that's not possible. Test: m on qualcomm device which only contains SKU specific manifests Change-Id: I3e4e8f9087640608643cc726bcfa0658467745eb
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.