| commit | c3eefb6d3d0d285942db6f496eabeee3eea62a98 | [log] [tgz] |
|---|---|---|
| author | Devin Moore <devinmoore@google.com> | Mon Oct 21 22:39:44 2024 +0000 |
| committer | Devin Moore <devinmoore@google.com> | Mon Oct 21 22:56:21 2024 +0000 |
| tree | 8e93c957d9cca2202f6e8a0a02d2879548eada5e | |
| parent | 9b1b1e03ff2a365674e9d13428b837c4f4ff5542 [diff] |
Support a raw bootconfig file as input to vendor-bootconfig.img Make variables can only get us so far... This allows for more of the supported input formats for boot config, like spaces in the values. Ex: foo=this will work in a file If that is in a file, it will be added to the vendor-bootconfig.img as-is. If it is in the BOARD_BOOTCONFIG variable, it gets chopped up to look like multiple different arguments like: foo=this will work in a file Test: build with/without BOARD_BOOTCONFIG and BOARD_BOOTCONFIG_FILE Test: verify contents of vendor-bootconfig.img in all 4 combos Test: verify "bootconfig" kernel cmdline arg doesn't show up in vendor_boot.img when neither variable is set Bug: 374651835 Change-Id: If59b1a9c968799bacbd4d88e0191e6bddc81a361
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.