| commit | d728ee1a065aafa0d4833d4f01225738bfaa249a | [log] [tgz] |
|---|---|---|
| author | Jingwen Chen <jingwen@google.com> | Tue May 18 06:02:53 2021 +0000 |
| committer | Jingwen Chen <jingwen@google.com> | Tue May 18 23:37:39 2021 +0000 |
| tree | 02b7053a571092672cfd1f51ea576c0d9d3f830d | |
| parent | abd0ea8743901a2afe5ed724a92802b12476c50a [diff] |
Introduce `b` into envsetup.sh. `b` is a function that combines: 1. Integrated generation of a synthetic bazel workspace, containing symlinks to BUILD and bzl files alongside symlinks to the source tree. This is the --package_path of the bazel build. 2. Running the Bazel build itself with b's entire argv. A user accustomed to typing `bazel build <targets>` would now type `b build <targets>`. Test: source build/envsetup.sh; b build //bionic/...; b cquery --output=label_kind //bionic/... Fixes: 188490434 Change-Id: I36e366108b024c09945d764a1115786658e03681
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.