| commit | 5ca4f682608dc68d7c32f4ab70742fa504514b30 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Thu Feb 06 15:22:28 2025 -0800 |
| committer | Cole Faust <colefaust@google.com> | Thu Feb 06 15:47:55 2025 -0800 |
| tree | 19a15053f2ae3b949029c3af451cc9a0a0490037 | |
| parent | bfe94d676195e6f967f16f66dd0ffff856398840 [diff] |
Remove output_file before generating it aosp/3478832 recently switched some fsv_meta files to symlinks. The symlink creation and file writing operations in most programming languages don't work properly when the destination is already exists and is of the opposite type. (symlinking on top of an existing file/ symlink would fail, file writing would write through the symlink) Remove the output file first. This wasn't noticed origionally because it only happens on certain types of incremental builds, and is also fixed if you run an `m installclean`. Bug: 394404628 Test: m Change-Id: I7f900d52b81bb696e597f20f20a092987e42db2e
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.