| commit | 2bdaea7e20c0abaaf56c9f18afbe0bb02a89c02f | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Fri Apr 26 00:20:10 2024 +0000 |
| committer | Spandan Das <spandandas@google.com> | Mon Apr 29 21:31:31 2024 +0000 |
| tree | b673febde4b05d00a3ab6f0a2fe2a8a5f41241ff | |
| parent | 013330b02889e12d8cc8f23c91f5f7cff7e985d6 [diff] |
Move coverage builds prebuilt special case to make Having this in make has the following advantages - allows this to be used in other places in make that are sensitive to prebuilt selection, e.g. apex boot jars that are present in source but not in prebuilt apexes - collocates the various prebuilt special edge cases Test: presubmits Test: in internal, lunch cf_x86_64_phone-next-userdebug Test: EMMA_INSTRUMENT_FRAMEWORK=true get_build_var PRODUCT_BUILD_IGNORE_APEX_CONTRIBUTION_CONTENTS true Bug: 308188056 Change-Id: I3e81b348e9f1e72e6d120a881d37356c413b005b
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.