| commit | 172c8e6de0b02135bf7755c73b41c096c1a1cbc0 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Wed Sep 25 18:24:53 2019 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Sun Oct 13 04:18:05 2019 +0900 |
| tree | 011a1b6271751e955261eab83d1140c6e3024c1b | |
| parent | 0ffe0c6248218ee49fc3affec66de557136c11d9 [diff] |
install VNDK APEX instead of VNDK libs VNDK APEX replaces VNDK libs under /system/libs/vndk[-sp]. For current VNDK (vndk_package), com.android.vndk.current APEX is installed instead of VNDK libraries. For older versions of VNDK (vndk_snapshot_package), com.android.vndk.v## APEXes are installed along with prebuilt VNDK libs. The reason why phony targets of VNDK prebuilts are still installed is that phony targets install the required *.libraries.##.txt files to /system/etc. After those .txt files are moved to APEXes, then we can remove those phony targets.(b/141450808) Bug: 141451661 Test: m && boot (tested with cuttlefish) Change-Id: Ibfa06d42ec0081fa7010091ef097bb940bacf8d6
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.