commit | be6f3a146d2261b0a081818bcbde351b17f6b219 | [log] [tgz] |
---|---|---|
author | Jooyung Han <jooyung@google.com> | Tue Dec 13 18:21:56 2022 +0900 |
committer | Jooyung Han <jooyung@google.com> | Tue Dec 13 18:21:56 2022 +0900 |
tree | 3a3513ac0c53305fc507a57331d8313e229193d5 | |
parent | 2dcc38701b38bddf62e4dfc25d9e063ba5e5f203 [diff] |
Remove linkerconfig from base_system Linkerconfig is served by com.android.runtime APEX which is already listed in base_system (via runtime_libart.mk). Bug: 260982509 Bug: 262330207 Test: MicrodroidAppTest Test: vm run-microdroid Change-Id: I2451526cb42be1ad60dcec3ae477fad2b9df9f83
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.