| commit | 49bf691c654f3fadfc54a4a5abd9c2093fdb3e39 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Thu Mar 09 16:36:37 2023 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Thu Mar 09 16:47:32 2023 +0900 |
| tree | 502e99f40ebd4561b4106937cd6e4ebb11945590 | |
| parent | cee4ebf1c3456f48e6b919ba4b681012bd43f227 [diff] |
Remove the old output of conv_linker_config
With 3397b6a2aadf8c2eb808fa38f7d6c07d5c82f320 in build/soong,
conv_linker_config fails when the output exists.
For system/vendor partitions, linker.config.pb files are built by
a custom rule, which is missing the removal of the old output. It would
fail with incremental build.
We could fix this by adding --force to overwrite. But I just added `rm`
following the convention in Makefile.
Bug: n/a
Test: m && (touch input of /vendor/etc/linker.config.pb)
m (again)
Change-Id: Iaeaf861e90b9535394d94c6b16229a4f566789d5
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.