| commit | da2d4a29bf21e0375b40d2654619e529978cf97f | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Mon Jan 09 16:26:23 2023 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Tue Jan 10 11:57:23 2023 +0900 |
| tree | 105bf1bca43279c1f851775ba3647ef81a0debe3 | |
| parent | 5c35eed41615dd450fd91b9a2b7893649edd3b72 [diff] |
vendor/etc/linker.config.pb from multiple input files When we have dedicated .mk files for each modules (e.g. usb, drm, etc) and those modules have their own linker configuration requirements, it would make more sense to have "fragments" for linker configuration. This change introduces a new list variable to store the list of linker configuration fragments. When it's set, vendor/etc/linker.config.pb is generated from the list of input fragments. Bug: 264330513 Test: set PRODUCT_VENDOR_LINKER_CONFIG_FRAGMENTS Test: m vendorimage (generates vendor/etc/linker.config.pb) Change-Id: I9eed0f90add0191885b7195efdab94b5b1a4a62d
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.