commit | 28810e40d8cc5218ed255070f058b1b863534ea5 | [log] [tgz] |
---|---|---|
author | Spandan Das <spandandas@google.com> | Tue Oct 22 00:21:36 2024 +0000 |
committer | Spandan Das <spandandas@google.com> | Tue Oct 22 00:21:36 2024 +0000 |
tree | 8a79725a4a9718216c205cc7a2277e8076114c75 | |
parent | 87cf780578a81409c33efb3fa7ca4dfd74ff147d [diff] |
Export BUILDING_VENDOR_IMAGE to soong If true, soong will autogenerate a partition module for vendor.img Bug: 374371755 Test: verified that no vendor partition is created for aosp_x86_64 Test: verified that vendor partition is created for aosp_cf_x86_64_phone Change-Id: I15dac7f72c2d34f928dccf5d6e4c608500c9b400
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.