| commit | bfa114d05b0d325ad46b479320dc23d63985c6a1 | [log] [tgz] |
|---|---|---|
| author | Jingwen Chen <jingwen@google.com> | Thu Jun 17 05:42:43 2021 +0000 |
| committer | Jingwen Chen <jingwen@google.com> | Mon Jun 21 06:12:33 2021 +0000 |
| tree | a31d8650bef2b05156198f6880d0bed59e7d338a | |
| parent | bb53fe394bb1a8d36bf48806f7d1cebaa0117239 [diff] |
Direct Bazel builds from m. This CL extends the `m` function to short circuit to Bazel iff: 1) USE_BAZEL_ANALYSIS is set to 1 or true 2) There is only 1 Soong module requested to be built 3) The Soong module has a corresponding Bazel alias target in @soong_injection//targets/BUILD to the real target in out/soong/workspace. Test: TH Change-Id: I976ffa53106c0b52c75b71f1e0e1e8b3ef5cb3d1
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.