| commit | 0b7b97bfc3034eb356fae5aba766938ba6295aa0 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Tue Mar 31 17:04:54 2020 +0900 |
| committer | Jiyong Park <jiyong@google.com> | Tue Mar 31 17:04:54 2020 +0900 |
| tree | f844e9977943afd2286985ac0dc8d541ee5fc3a7 | |
| parent | 7ee9edff6743a43cd48a06d4f9464c5b35eae943 [diff] |
libselinux is LLNDK, not VNDK-core libselinux has stable C APIs and therefore provides a stub library for Mainline clients. It is not copied into any Mainline modules and the only instance of the lib in /system/lib serves all of them. However for vendors, we still had another copy of libselinux in VNDK (e.g. in the VNDK APEX that is served via the path /system/lib/vndk). Since the library is guaranteed to have stable C APIs, there is no reason to keep the vendor variant of the library in VNDK. Keeping it in VNDK would be just a waste of storage space. This change removes libselinux from VNDK and marks it as LLNDK. The single instance of if in /system/lib serves vendor processes as well as Mainline modules. Bug: 151303316 Test: m Change-Id: I7106ac236770b55b147c8a7f524bc2eddbddedb1
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.