| commit | 6871bbf91ea92e86d82fcc2d56f2c8b89a06d670 | [log] [tgz] |
|---|---|---|
| author | Peiyong Lin <lpy@google.com> | Wed Apr 26 01:07:35 2023 +0000 |
| committer | Peiyong Lin <lpy@google.com> | Thu Apr 27 22:36:36 2023 +0000 |
| tree | 45e49b9fefd27e775bf35be313c76f4bbc1d5132 | |
| parent | 2467b20cecfcf9d6fc5df7b4fbcfda0dd5f4540a [diff] |
Properly define angle.mk Previously we used USE_ANGLE to determine whether the build should include ANGLE drivers, this patch consolidates that into a separate Makefile. Bug: b/270994705 Test: atest CtsAngleIntegrationHostTestCases Change-Id: I4d7ffb869ced219009446d907230178e4b940157 Merged-In: I4d7ffb869ced219009446d907230178e4b940157
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.