| commit | eacf20b7aaf13523c04cc389abe5f1cdeb778f5e | [log] [tgz] |
|---|---|---|
| author | Christian Oder <myself5@carbonrom.org> | Sun Sep 06 14:54:15 2020 +0200 |
| committer | LuK1337 <priv.luk@gmail.com> | Sat Oct 19 00:16:01 2024 +0200 |
| tree | 5627bef91f4e62996ff5d20e66aa6cd36f84395c | |
| parent | e5e4e7fa9eaa3aae241ce470c7267808f8bf1b40 [diff] |
build_image: Allow disabling custom inode count calculation This allows us to skip custom inode count calculation by setting BOARD_*IMAGE_EXTFS_INODE_COUNT to -1, this will end up letting mke2fs calculate appropriate inode count on its own. While build_image only allocates exact number of needed inodes plus 4% spare with .2% margin, mke2fs will allocate as many inodes as it thinks is appropriate given the filesystem size. Change-Id: If03d5edae8378be3b305346176067b01163f6f3d
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.