| commit | 36481e0b340149a240a11c51d4fc8736a712aae6 | [log] [tgz] |
|---|---|---|
| author | Kiyoung Kim <kiyoungkim@google.com> | Mon Nov 16 10:50:05 2020 +0900 |
| committer | Kiyoung Kim <kiyoungkim@google.com> | Tue Dec 01 15:33:09 2020 +0900 |
| tree | 8c831c72c9b5b4bc492e8b9a8952c7fe4e899540 | |
| parent | e13277f26e7040cbd20e5d310ccd0e771d9330a3 [diff] |
Generate system stub library list at build time List of stub libraries from system (and bionic APEX) is currently managed in static file. This change generates the list at build time and adds to the system config so linkerconfig can use it. Bug: 172889962 Test: Build cuttlefish and confirmed list is generated in /system/etc/linker.config.pb Change-Id: Idd5a93442f398dd8e88c767c694ddae64d1bb713
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.