Lines Matching full:bazel
3 title: "Using Bazel"
4 linkTitle: "Using Bazel"
10 Skia is currently migrating towards using [Bazel](https://bazel.build/) as a build system, due to
14 [Bazel label notation](https://bazel.build/concepts/labels), so to refer the file located at
17 ## Learning more about Bazel
18 The Bazel docs are quite good. Suggested reading order if you are new to Bazel:
19 - [Getting Started with Bazel and C++](https://bazel.build/tutorials/cpp)
20 - [WORKSPACE.bazel and external deps](https://bazel.build/docs/external)
21 - [Targets and Labels](https://bazel.build/concepts/labels)
22 - [Understanding a build](https://bazel.build/docs/build)
23 - [Configuration with .bazelrc files](https://bazel.build/docs/bazelrc)
25 Googlers, check out [go/bazel-bites](http://go/bazel-bites) for more tips.
27 ## Building with Bazel
32 ### Linux Hosts (you are running Bazel on a Linux machine) argument
35 bazel build //example:hello_world_gl
40 `//examples/BUILD.bazel` named "hello_world_gl", which uses the `sk_app` framework
43 Bazel will put this executable in `//bazel-bin/example/hello_world_gl` and tell you it did so in
44 the logs. You can run this executable yourself, or have Bazel run it by modifying the command to
47 bazel run //example:hello_world_gl
50 If you want to pass one or more flags to `bazel run`, add them on the end after a `--` like:
52 bazel run //example:hello_world_gl -- --flag_one=apple --flag_two=cherry
55 ### Mac Hosts (you are running Bazel on a Mac machine) argument
58 bazel build //example:bazel_test_exe
65 Our Bazel toolchain assumes you have `xcode-select` in your path so that we may symlink the
70 You should make a [.bazelrc file](https://bazel.build/docs/bazelrc) in your home directory where
74 Skia defines some [configs](https://bazel.build/docs/bazelrc#config), that is, group of settings
75 and features in `//bazel/buildrc`. This file contains configs for builds that we use regularly
78 If you want to define Skia-specific configs (and options which do not conflict with other Bazel
79 projects), you make a file in `//bazel/user/buildrc` which will automatically be read in. This
82 You may want some or all of the following entries in your `~/.bazelrc` or `//bazel/user/buildrc`
87 and using this as the location for the Bazel sandbox can dramatically improve compile times because
88 [sandboxing](https://bazel.build/docs/sandboxing) has been observed to be I/O intensive.
95 …bly bypass sandboxing as [it is known to be slow](https://github.com/bazelbuild/bazel/issues/8230).
101 We are in the process of setting up Remote Build Execution (RBE) for Bazel. Some users have reported
119 Add the following to `//bazel/user/buildrc` if you are on a Linux x64 box and want to be able to
122 build --host_platform=//bazel/platform:linux_x64_hermetic