.bazelrc

build --enable_bzlmod=false

build --action_env="BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1"

build:clang --extra_toolchains=//toolchain:clang
build:gcc   --extra_toolchains=//toolchain:gcc

build:clang-format --aspects @bazel_clang_format//:defs.bzl%clang_format_aspect
build:clang-format --@bazel_clang_format//:binary=@llvm_toolchain//:clang-format
build:clang-format --@bazel_clang_format//:config=//:format_config
build:clang-format --output_groups=report
build:clang-format --keep_going

build:clang-tidy-base --config=clang
build:clang-tidy-base --aspects @bazel_clang_tidy//clang_tidy:clang_tidy.bzl%clang_tidy_aspect
build:clang-tidy-base --@bazel_clang_tidy//:clang_tidy_config=//:tidy_config
build:clang-tidy-base --output_groups=report
build:clang-tidy-base --keep_going

build:verbose-clang-tidy --config=clang-tidy-base
build:verbose-clang-tidy --@bazel_clang_tidy//:clang_tidy_executable=//tools:verbose-clang-tidy

build:clang-tidy --config=clang-tidy-base
build:clang-tidy --@bazel_clang_tidy//:clang_tidy_executable=@llvm_toolchain//:clang-tidy

try-import %workspace%/user.bazelrc

build --workspace_status_command=tools/bazel_workspace_status.sh
# Do not load LD_LIBRARY_PATH from the environment. This leads to more cache hits
# when triggering builds using different shells on the same machine.
# https://stackoverflow.com/questions/74881594/bazel-builds-from-scratch-ignoring-cache
build --incompatible_strict_action_env

coverage --combined_report=lcov
coverage --experimental_generate_llvm_lcov
# Needed because our tests are in a different package than the code they test.
coverage --instrumentation_filter='//.*'

# buildbuddy suggestions. Doesn't hurt to have them always.
build --nolegacy_important_outputs
build --remote_cache_compression