| commit | 7b43b96b9472d0e371e3b833b224e59fe22dfdd4 | [log] [tgz] |
|---|---|---|
| author | Ashutosh Agarwal <radsaggi@google.com> | Tue Oct 08 10:42:37 2024 +0000 |
| committer | Ashutosh Agarwal <radsaggi@google.com> | Tue Oct 08 10:42:37 2024 +0000 |
| tree | 94ef8789ee72dd7b60ddeac8a6b3d4da8c6340d1 | |
| parent | 1b9d4505aec5663e91f1b351ac00b705ca7cb4f9 [diff] |
Add capability to let devices specify linker config fragments for /product partition. PRODUCT_PRODUCT_LINKER_CONFIG_FRAGMENTS to build product/etc/linker.config.pb is added to the core build Makefile. This is used to support product-specific linker config fragments. Bug: 369573086 Change-Id: Id964e70731389e106190dcac92fa9ff98bef6d80 Test: manual
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.