| commit | 1f9b8f0cc6fe9a1e65eb33218bd77e75a85e4310 | [log] [tgz] |
|---|---|---|
| author | Bill Peckham <bpeckham@google.com> | Wed Jul 03 15:58:48 2019 -0700 |
| committer | Bill Peckham <bpeckham@google.com> | Wed Jul 03 15:58:48 2019 -0700 |
| tree | 303106e7213116841867939b1ce0b53ba1868d20 | |
| parent | 28142690baa94cbe91aa19183de6a0666a7498b1 [diff] |
Move definition of create-vendor-odm-symlink within BUILDING_VENDOR_IMAGE When we build the system image separately from the vendor image, we need the /vendor/odm link (if any) to be created in the vendor build, not the system build. This change moves the create-vendor-odm-symlink function outside the BUILDING_SYSTEM_IMAGE gaurd, and inside the BUILDING_VENDOR_IMAGE gaurd. Bug: 136516335 Test: Build vendor image, verify that /vendor/odm -> /odm Change-Id: I6edf5d6d1fa0b2f632f67113f69a49b43f719941
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.