| commit | 9814ff11abc85324c652ec6ab4e5d7b034f1a9ac | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Thu Feb 13 17:45:08 2025 -0800 |
| committer | Cole Faust <colefaust@google.com> | Thu Feb 13 17:45:08 2025 -0800 |
| tree | a0521eabf160f05089fb561df80346f6811bcb4e | |
| parent | acd8beb0aa1a364e453d14d4a04ba3006c4aa659 [diff] |
Remove requirement that fsv_meta file is next to its input file In soong-built partitions, we will generate fsv_meta files before a partition staging directory is generated. This means that the source file will be some module-specific intermediates path, and the dest file will be a path local to the filesystem module. Relax the requirement that fsv_meta files are next to the files they protect. Bug: 394404628 Test: m aosp_shared_system_image, verified it didn't change before/after Change-Id: I6bbbd23aa93b15220c5b2302cb0b229e8f8de69c
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.