forked from ray-project/ray
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path.bazelrc
26 lines (26 loc) · 1.19 KB
/
.bazelrc
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
# build config
build --compilation_mode=opt
build --action_env=BAZEL_LLVM
build --action_env=BAZEL_SH
build --action_env=PATH
build --action_env=PYTHON2_BIN_PATH
build --action_env=PYTHON3_BIN_PATH
# Use Clang-Cl (Clang front-end with Visual C++ backend) on Windows
build --action_env=USE_CLANG_CL=1
# Enable build:windows, build:linux, build:macos, build:freebsd
build --enable_platform_specific_config
# Warnings should be errors
build --per_file_copt=-.*/arrow/util/logging.cc@-Werror
# Ignore warnings for protobuf generated files and external projects.
build --per_file_copt='\\.pb\\.cc$@-w'
build --per_file_copt='external/.*@-w'
# Ignore minor warnings for host tools, which we generally can't control
build --host_copt="-Wno-builtin-macro-redefined"
build --host_copt="-Wno-inconsistent-missing-override"
build --host_copt="-Wno-microsoft-unqualified-friend"
# This workaround is needed due to https://github.com/bazelbuild/bazel/issues/4341
build --per_file_copt="external/com_github_grpc_grpc/.*@-DGRPC_BAZEL_BUILD"
build --http_timeout_scaling=5.0
# This workaround is due to an incompatibility of
# bazel_common/tools/maven/pom_file.bzl with Bazel 1.0
build --incompatible_depset_is_not_iterable=false