Lines Matching +full:build +full:- +full:docs

3 *Warning* The Bazel build is experimental and best-effort, supported in line
5 [LLVM's peripheral support tier](https://llvm.org/docs/SupportPolicy.html).
6 LLVM's official build system is CMake. If in doubt use that. If you make changes
7 to LLVM, you're expected to update the CMake build but you don't need to update
8 Bazel build files. Reviewers should not ask authors to update Bazel build files
9 unless the author has opted in to support Bazel. Keeping the Bazel build files
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
16 The main motivation behind the existence of an LLVM Bazel build is that a number
19 another build system). Community members are also welcome to use Bazel for their
20 own development as long as they continue to maintain the official CMake build
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
31    https://docs.bazel.build/versions/main/install.html.
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`
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
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),
74 which will cache build results
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