| commit | d14e8941fb3e8bd8671ffa424955540c8f9cbb3c | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Wed Feb 05 15:38:28 2025 -0800 |
| committer | Cole Faust <colefaust@google.com> | Thu Feb 06 10:16:08 2025 -0800 |
| tree | 64d1389763fcef14a24f5d52af4a4ed47aa57957 | |
| parent | fee5677cc5d7a335262659488c38bcd804793ca4 [diff] |
Don't read through symlinks in fsverity_metadata_generator We're trying to change the build system to remove the need for a staging directory, where all the files are in the same location as they are on the device. This means that fsverity_metadata_generator will no longer be able to read through symlinks, because the files that the symlink is trying to point to won't be at the same location. Instead, when seeing a symlink, make the corresponding fsv_meta file also a symlink. Bug: 394404628 Test: atest ComposHostTestCases Change-Id: I857f135ff0825971b7779719576e2f931995e481
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.