Lines Matching +full:runs +full:- +full:on
3 *Warning* The Bazel build is experimental and best-effort, supported in line
10 up-to-date is on the people who use the Bazel build.
12 [Bazel](https://bazel.build/) is a multi-language build system focused on
17 of projects that depend on LLVM use Bazel, and Bazel works best when it knows
22 [proposal](https://github.com/llvm/llvm-www/blob/main/proposals/LP0002-BazelBuildConfiguration.md)
27 1. `git clone https://github.com/llvm/llvm-project.git; cd llvm-project` if
36 4. The `bazel build` command depends on the local compiler you want to use.
40 The `--config=generic_clang` flag by default sets the compiler to be `clang`
41 binary on the `PATH`.
43 bazel build --config=generic_clang @llvm-project//...
45 To provide a specific path to your `clang`, use the `--repo_env` Bazel flag.
48 bazel build --config=generic_clang --repo_env=CC=/usr/bin/clang --repo_env=CXX=/usr/bin/clang++ @llvm-project//...
50 6. If you are using **gcc** or **MSVC**, instead of `--config=generic_clang`
51 , pass `--config=generic_gcc` or `--config=generic_msvc`, which sets the
52 compiler to be `gcc` binary on the `PATH`.
54 bazel build --config=generic_gcc @llvm-project//...
56 To provide a specific path to your `gcc`, use the `--repo_env` Bazel flag.
59 bazel build --config=generic_gcc --repo_env=CC=/usr/bin/gcc --repo_env=CXX=/usr/bin/g++ @llvm-project//...
64 The repository `.bazelrc` will import user-specific settings from a
69 build --config=generic_clang
73 [disk caching](https://docs.bazel.build/versions/main/remote-caching.html#disk-cache),
77 build --disk_cache=~/.cache/bazel-disk-cache
81 [--sandbox_base](https://docs.bazel.build/versions/main/command-line-reference.html#flag--sandbox_base),
87 build --sandbox_base=/dev/shm
97 platform-specific are selected for in defines. Many are also hardcoded to the
103 A [Buildkite pipeline](https://buildkite.com/llvm-project/upstream-bazel)
104 runs the full Bazel build on every commit to the main branch. Notifications of
106 [llvm-bazel-alerts google group](https://groups.google.com/g/llvm-bazel-alerts),
108 on each failure using Buildkite's built-in notification system, so if you
111 on status change or routed based on blamelist are TODO (contributions welcome).