Default journal_size and extfs_rsv_pct for user specified mount point build_image.py implicitly adds some properties on top of the properties in the user provided prop file. Some of these were added only when mount_point was not explicitly specified. This was causing a difference in *.img created by Make and Soong. The latter explicitly specificies `mount_point` in the prop file. To fix these issues, the implicit addition has been copied over to the main parser. Bug: 419860251 Test: lunch husky-trunk_staging-userdebug Test: m out/target/product/husky/system_ext.img out/soong/.intermediates/build/soong/fsgen/husky_generated_system_ext_image/android_common/system_ext.img Test: verified that both are bit-identical Change-Id: I4167cfc813be94fdf80ec9c830a1aa63bbe56f9f
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.