f58dabce58
Without the -d $(TARGET_OUT) option for mkbootfs, only the compiled-in fs_config (from AOSP) is used for the generated ramdisk image. Device-specific additions are ignored. This is why AOSP sets this option for both the boot- and recovery ramdisk [1]. However, the option was removed for the recovery ramdisk in review.lineageos.org/c/LineageOS/android_build/+/222722 This causes device-specific fs_config additions to be ignored when generating the recovery ramdisk, potentially setting the wrong permissions. [1]: android.googlesource.com/platform/build/+/refs/tags/android-9.0.0_r37/core/Makefile#1388 Change-Id: I0f77a49d8b2f08791e60b34ddbb6f3b32bc2f0bc
Android Make Build System
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.