| commit | 0c0795944c6bb6a7f1d0e6d98a208051fd9b68ad | [log] [tgz] |
|---|---|---|
| author | Kiyoung Kim <kiyoungkim@google.com> | Thu Dec 01 10:15:10 2022 +0900 |
| committer | Kiyoung Kim <kiyoungkim@google.com> | Thu Dec 01 10:58:38 2022 +0900 |
| tree | 8998878cf0e2de7160ac982b59c1581decc42f31 | |
| parent | dd026fce63c5378e8305b86b48c79bf57b192ce0 [diff] |
Append LLNDK libraries in the APEX to the system linker config Some of the LLNDK libraries are in the APEX, and those should be marked as required libs of system image, so system namespaces can link to the APEX namespace properly. This change automates the process instead of adding APEX LLNDKs to linker.config.json manually. Bug: 251782700 Test: Cuttlefish build and boot succeeded Change-Id: I538a619caa67e64e6432517e1de87f3007bccbde
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.