| commit | d9a520c5bd4bdeb27a71a016fb5fbecdca687aaf | [log] [tgz] |
|---|---|---|
| author | Daniel Rosenberg <drosen@google.com> | Fri Oct 13 17:22:44 2023 -0700 |
| committer | Daniel Rosenberg <drosen@google.com> | Mon Nov 27 18:09:18 2023 -0800 |
| tree | e5e856905a3d4616f95f4a106dcd9df3a5d66ff3 | |
| parent | 8faa4a588001cad91b98a7577373745752a29971 [diff] |
Add support for different F2FS block sizes F2FS has been expanded to allow for different block sizes. Currently the block size must be the same as page size, but this may change in the future. This gives support for 16K while not restricting the ability to choose a block size that isn't based on the page size later on. Bug: 279820706 Test: Boot 16k F2FS device Change-Id: I4e025d83a5e5ad03d89bc80b02fea390c2cbad69
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.