commit | 2a0ed36bd994e953be93ca35bb15a35c12b023f9 | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Wed Dec 26 17:32:56 2018 +0900 |
committer | Jiyong Park <jiyong@google.com> | Fri Jan 11 13:44:20 2019 +0900 |
tree | 84c600ce88bed828b859be3e9446c602fd2652ad | |
parent | bdf0ec03b67f044fa9f9d1a5ab488b0fe96445b5 [diff] |
Install bootstrap variant of bionic libs Bionic libs are moved to the runtime APEX and thus are available via the path /apex/com.android.runtime/lib[64]. However, for processes that are started before the APEX is ready, a copy of the bionic libs should be left under /system/lib[64]. This change ensures that the bootstrap bionic libs are always installed to the system partition. Note that, at runtime, the bionic libs in the runtime APEX are bind-mounted to /system/lib/<libname>.so which essentially hides the bootstrap bionic libs to the processes after the activation of the runtime APEX. Bug: 120266448 Test: m and check that libc, libdl, libm are under /system/lib[64] Change-Id: I9d5e8e718aa020c012f312a70ed54652130048dd
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.