| commit | 7650ddad013dc0bad6d0d614c08a504345a9ee90 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Wed Jul 05 15:58:53 2023 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Thu Jul 06 13:45:12 2023 +0900 |
| tree | 833b8684b90c85a1fc86cc51111f0a9577b06cd2 | |
| parent | 82d233a1bd63c695161a53b347872b1c4296ceb6 [diff] |
Install vintf_fragments even when they are shared
Vintf_fragments should be installed regardless when they are shared with
other modules or not.
cc_binary {
name: "foo",
vintf_fragments: ["shared.xml"],
}
cc_binary {
name: "bar",
vintf_fragments: ["shared.xml"],
}
Either `m bar` or `m foo` should install `shared.xml`.
Previously, only *new* vintf_fragments were installed, which means, one
of "foo" or "bar" didn't trigger the installation of "shared.xml".
Bug: 198818343
Test: (see above)
Change-Id: I52b831df046b585db41449f06a6f9c684d623468
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.