| commit | a8d1143beb13a9f3cbe802d626d7eb9b12fbdc5e | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Mon Nov 07 21:37:06 2022 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Wed Nov 09 18:22:14 2022 +0000 |
| tree | da29900866bc90667500df5dc963fce13ccc4d80 | |
| parent | 56a6905d86ab7267e73ffda4c15a8dd01284e5bb [diff] |
Update deapexer call to explictly use blkid To support erofs apex extract via deapexer, we need blkid to tell the filesystem type of underlying payload image. If it is ext4, debugfs_static will be used, if it is erofs, then we should use fsck.erofs. Thus we now need explicit blkid input. Also, remove dependency on fsck.erofs for other deapexer calls. Only extract deapexer call needs blkid and fsck.erofs. BUG: b/255963179, b/240288941 Change-Id: I8cea0f2def664f9cabf8b14c9a7ecc47bbddfbdd
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.