| commit | 50978e8640a3705cf81b36dff79d3bb297e66085 | [log] [tgz] |
|---|---|---|
| author | Isaac Chen <ycchen@google.com> | Fri Jul 13 18:52:42 2018 +0800 |
| committer | Isaac Chen <ycchen@google.com> | Tue Jul 17 10:10:31 2018 +0800 |
| tree | 700ebc237f580123a35b91bad6f17cc95bb2658b | |
| parent | 87399730de1dc8d6002d59feca1b25764843769a [diff] |
Create extra symbolic links at root for arm64 GSI
Relevant firmware/SW components have been moved out of directories
under root, but not all references to them updated. For example,
/vendor/firmware_mnt won't be used by Android to load firmware.
So we still need these symlinks so the firmware/SW components can
be accesses.
These links should be removed after all references are updated.
Bug: 111287060
Test: $ lunch aosp_arm64-userdebug; m -j
# Checked $OUT/root for the added links
Change-Id: Ia7915dbdeabdee7a5cf8851772e89f080b927c45
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.