| commit | 8ab6603a430d0355778fa02faf2ce6f64f9b21a8 | [log] [tgz] |
|---|---|---|
| author | Dmitrii Merkurev <dimorinny@google.com> | Tue May 17 23:10:37 2022 +0000 |
| committer | Dmitrii Merkurev <dimorinny@google.com> | Tue May 17 23:10:37 2022 +0000 |
| tree | d2145c0deee29d2dd45c660795cb41bf106e1da6 | |
| parent | d528b3c55389139ef1ebcf22633c5aca52fe50b7 [diff] |
Introduce EROFS compress hints to the Android build system Make it possible to provide a prebuilt hints file to specify different compression strategies on a file basis for all partitions using: BOARD_EROFS_COMPRESS_HINTS := <path>/erofs-hints.txt or separately for every partition using: BOARD_SYSTEMIMAGE_EROFS_COMPRESS_HINTS := <path>/system-partition-erofs-hints.txt BOARD_VENDORIMAGE_EROFS_COMPRESS_HINTS := <path>/vendor-partition-erofs-hints.txt Hints format: Each line is defined by tokens separated by spaces in the following form: <pcluster-in-bytes> <match-pattern> pcluster-in-bytes can be specified as 0 which mean file will not be compressed Bug: 231934752 Test: used dump.erofs -S system.img to verify the system image isn't compressed after specifying BOARD_SYSTEMIMAGE_EROFS_COMPRESS_HINTS := no-compress.txt, where no-compress.txt contains 0 .* Test: used dump.erofs --nid=<inode-for-all-apk-files> vendor.img to verify apk files are not compressed (the rest of the partition content is compressed) Test: used dump.erofs -S <all-images> to verify all images are not compressed after specifying BOARD_EROFS_COMPRESS_HINTS := <path>/no-compress.txt Change-Id: I64054e26af5ea5781c45d2183b7796a9ad2b7927
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.