# TODO: ErrorProne's SelfAssertions are violated in tests
build --javacopt=-Xep:SelfAssertion:WARN

build:dbg --compilation_mode=dbg

build:opt --compilation_mode=opt

build:san-common --config=dbg --strip=never --copt=-O1 --copt=-fno-omit-frame-pointer
# TODO ASAN hits ODR violations with shared linkage due to
# cc_proto_library cyclic dependency.
build:san-common --dynamic_mode=off

build:asan --config=san-common --copt=-fsanitize=address --linkopt=-fsanitize=address

build:msan --config=san-common --copt=-fsanitize=memory --linkopt=-fsanitize=memory
build:msan --copt=-fsanitize-memory-track-origins
build:msan --copt=-fsanitize-memory-use-after-dtor
build:msan --action_env=MSAN_OPTIONS=poison_in_dtor=1

# Use our instrumented LLVM libc++ in Kokoro.
build:docker-msan --config=msan
build:docker-msan --linkopt=-L/opt/libcxx_msan/lib --linkopt=-lc++abi
build:docker-msan --linkopt=-Wl,-rpath,/opt/libcxx_msan/lib
build:docker-msan --cxxopt=-stdlib=libc++ --linkopt=-stdlib=libc++


build:tsan --config=san-common --copt=-fsanitize=thread --linkopt=-fsanitize=thread

build:ubsan --config=san-common --copt=-fsanitize=undefined --linkopt=-fsanitize=undefined
build:ubsan --action_env=UBSAN_OPTIONS=halt_on_error=1:print_stacktrace=1
# Workaround for the fact that Bazel links with $CC, not $CXX
# https://github.com/bazelbuild/bazel/issues/11122#issuecomment-613746748
build:ubsan --copt=-fno-sanitize=function --copt=-fno-sanitize=vptr
# Abseil passes nullptr to memcmp with 0 size
build:ubsan --copt=-fno-sanitize=nonnull-attribute

# Workaround Bazel 7 remote cache issues.
# See https://github.com/bazelbuild/bazel/issues/20161
build --experimental_remote_cache_eviction_retries=5
build --remote_download_outputs=all

# Build with all --incompatible flags that we can. This helps us prepare for
# upcoming breaking changes in Bazel. This list was generated for Bazel 6 by
# running bazelisk with the --migrate flag and filtering out all flags that
# default to true or are deprecated.
build --incompatible_check_sharding_support
build --incompatible_config_setting_private_default_visibility
build --incompatible_default_to_explicit_init_py
build --incompatible_disable_native_android_rules
build --incompatible_disable_starlark_host_transitions
build --incompatible_disable_target_provider_fields
build --incompatible_disallow_empty_glob
build --incompatible_dont_use_javasourceinfoprovider
build --incompatible_enable_android_toolchain_resolution
build --incompatible_enable_apple_toolchain_resolution
build --incompatible_exclusive_test_sandboxed
build --incompatible_remote_use_new_exit_code_for_lost_inputs
build --incompatible_sandbox_hermetic_tmp
build --incompatible_top_level_aspects_require_providers
build --incompatible_use_cc_configure_from_rules_cc

# We cannot yet build successfully with the following flags:
#   --incompatible_check_testonly_for_output_files
#   --incompatible_disallow_struct_provider_syntax
#   --incompatible_no_implicit_file_export
#   --incompatible_no_rule_outputs_param
#   --incompatible_stop_exporting_language_modules
#   --incompatible_strict_action_env
#   --incompatible_visibility_private_attributes_at_definition

# We might be compatible with these flags, but they are not available in all
# Bazel versions we are currently using:
#   --incompatible_disable_objc_library_transition
#   --incompatible_fail_on_unknown_attributes
#   --incompatible_merge_fixed_and_default_shell_env

# For easier debugging of build failures.
common --announce_rc
build --verbose_failures

# Important: this flag ensures that we remain compliant with the C++ layering
# check.
build --features=layering_check

build --enable_platform_specific_config