| commit | 69281c31bac7ee37f037e2509b73abbb9caa8745 | [log] [tgz] |
|---|---|---|
| author | Peter Collingbourne <pcc@google.com> | Fri Feb 23 22:38:54 2024 -0800 |
| committer | Peter Collingbourne <pcc@google.com> | Fri Feb 23 23:04:33 2024 -0800 |
| tree | 6dc80310d50b51b0b75d24da7ecc8765b3429321 | |
| parent | 3939d1ca5957571814933cc311655840a513677e [diff] |
Create empty /linkerconfig/ld.config.txt in ramdisk. This silences warnings such as: linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt" WARNING: linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt" that are printed at the start of every command in the first stage console. Change-Id: I3d820e4960a4dbca34369223aed83589534c2eb6
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.