commit | adcdb2fbdaa64b11851c71ea412cb9a2512d3f5a | [log] [tgz] |
---|---|---|
author | Inseob Kim <inseob@google.com> | Fri Jun 11 12:55:10 2021 +0900 |
committer | Inseob Kim <inseob@google.com> | Wed Jun 16 20:58:59 2021 +0900 |
tree | 78982fe08cff6e86c486e5c5f418e88ffd518f7d | |
parent | 1d4081b2a54e06fb44480de49ae070290c31caf4 [diff] |
Directly create ramdisk dirs in ramdisk image rule These directories have been created with post install cmds of init_first_stage. To migrate init_first_stage to Soong, the directory rules are now written directly in ramdisk image rule. Bug: 187196593 Test: "m installclean; m" and see ramdisk output Change-Id: Ic76c325ce102347f20b282572e3edbb5b4359aaf
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.