commit | d7cc7e8f9aa463c493219bd259e96b46e47ee8d7 | [log] [tgz] |
---|---|---|
author | Sandeep Dhavale <dhavale@google.com> | Mon Sep 11 22:25:53 2023 -0700 |
committer | Sandeep Dhavale <dhavale@google.com> | Wed Oct 18 08:23:36 2023 -0700 |
tree | 78d8bdca1f35794c8ef69b68406c3e9c25512ed1 | |
parent | 4f358fd4431f3efce41b59d8bdf056725da78da8 [diff] |
Add support for specifying erofs blocksize This change allows us to specify erofs filesystem block size which will be used to create erofs image. Either it can be specified at board level using BOARD_EROFS_BLOCKSIZE. Or per read only partition image using BOARD_<PARTITION>IMAGE_EROFS_BLOCKSIZE. Examples: BOARD_EROFS_BLOCKSIZE := 16384 OR BOARD_PRODUCTIMAGE_EROFS_BLOCKSIZE := 16384 Bug: 303316443 Test: m and file ${ANDROID_PRODUCT_OUT}/*.img Change-Id: I9bf3d299ae02165d0bffc62f474a302408d8b9b9 Signed-off-by: Sandeep Dhavale <dhavale@google.com>
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.