| commit | 6733381fceb44fe074e3586c7a94705c4d49a509 | [log] [tgz] |
|---|---|---|
| author | Bill Peckham <bpeckham@google.com> | Tue Aug 13 16:05:34 2019 -0700 |
| committer | Bill Peckham <bpeckham@google.com> | Tue Aug 13 16:05:34 2019 -0700 |
| tree | 9b24200b969f06d8283030ea1174563b26197870 | |
| parent | f51a70b009b3557b173e804f0da377f2aa5417c9 [diff] |
Avoid adding VINTF manifest fragment more than once. In the case of building a multilib library that defines LOCAL_VINTF_FRAGMENTS, the previous code would create duplicate rules for the fragment. This change uses the my_vintf_new_installed variable (which may be empty) to avoid the duplication. Bug: 139268165 Test: Verify that build warnings are gone, yet VINTF fragment still installed. Change-Id: I579ec650019a29a6a105118ad5e5ae9376e8d9bc
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.