Lines Matching full:bazel
10 - https://docs.bazel.build/versions/4.2.1/tutorial/cc-toolchain-config.html
11 …- https://github.com/emscripten-core/emsdk/blob/7f39d100d8cd207094decea907121df72065517e/bazel/ems…
34 …# https://docs.bazel.build/versions/main/skylark/lib/cc_common.html#create_cc_toolchain_config_info
36 …# https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/st…
62 Bazel normally restricts us to referring to (and therefore running) executables/scripts
64 to run are brought in via WORKSPACE.bazel and are located in EXEC_ROOT/external/clang....
68 These action_configs also let us dynamically specify arguments from the Bazel
72 …# https://cs.opensource.google/bazel/bazel/+/master:tools/cpp/cc_toolchain_config_lib.bzl;l=435;dr…
77 …# https://cs.opensource.google/bazel/bazel/+/master:tools/cpp/cc_toolchain_config_lib.bzl;l=488;dr…
105 # Bazel assumes it is talking to clang when building an executable. There are
115 …# https://github.com/emscripten-core/emsdk/blob/7f39d100d8cd207094decea907121df72065517e/bazel/ems…
118 …# https://docs.bazel.build/versions/main/cc-toolchain-config-reference.html#cctoolchainconfiginfo-…
201 # Bazel, it will declare the Build is not properly specified (that is,
202 # it appears to use headers outside of Bazel's control/view) and fail.
310 # Running a Bazel command with --features diagnostic will cause the compilation and
320 # Running a Bazel command with --features print_search_dirs will cause the link to fail