| commit | bc00e060cb0c9d72d68efcda590f8418051068e5 | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Mon Oct 28 22:53:24 2024 +0000 |
| committer | Spandan Das <spandandas@google.com> | Mon Oct 28 22:55:17 2024 +0000 |
| tree | 27e9d246afa3bebcfd9566f8109c3fbb6af33d06 | |
| parent | 37dd55dc8429ef6dc173f510f6f56619f1df0437 [diff] |
Export PRODUCT_VENDOR_LINKER_CONFIG_FRAGMENTS to soong This will be used to create linker.config.pb file in the autogenerated vendor `android_filesystem`. Test: verified that linker.config.pb is present in the autogenerated soong vendor.img Bug: 375686533 Change-Id: I3f0ef6322fdfe28fb77c8599d1c8871d187b74a5
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.