943fa4c523
If an AOSP target is built with dynamic partitions support but without vendor.img available at build time, don't write 'vendor' to dynamic_partitions_info.txt that will be used for building OTA packages. We can't remove the partition from BoardConfig file, because the name will be still needed in other places, such as generating the partition metadata (super_empty.img). Otherwise manually flashing vendor.img at a later point would require additional steps (e.g. `fastboot create-logical-partition`). Bug: 120852744 Test: `m -j dist` with and without vendor projects. Change-Id: Ia1c3ed5bbea0255f1908958140dac97a1597586d |
||
|---|---|---|
| common | ||
| core | ||
| packaging | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Android.mk | ||
| buildspec.mk.default | ||
| Changes.md | ||
| CleanSpec.mk | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| OWNERS | ||
| README.md | ||
| tapasHelp.sh | ||
| Usage.txt | ||
Android Make Build System
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.