commit | a69b809425234e0e35079c10e699c4ae451b207b | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Wed Nov 03 13:15:59 2021 -0700 |
committer | Colin Cross <ccross@android.com> | Mon Nov 08 15:23:32 2021 -0800 |
tree | 10391a3eed68e481251100e37224e1d5845aafb3 | |
parent | cf5c18aa8e10fed28a99c603d5611aa07dc0888f [diff] |
Don't create compatibility suite copy rules for installed path Don't create compatibility suite copy rules for $(LOCAL_BUILT_MODULE) to $(LOCAL_INSTALLED_MODULE), as that could conflict with a Soong install rule. Instead, always create the install rule the normal way, and replace the compatibility suite copy rule with a noop if it is the same as the normal rule. Bug: 204136549 Test: m checkbuild Change-Id: Ic8ac80eda8554fae2b7ecc2516165da020bdaebe
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.