From 51dc6fb1c1be2c9e59363cabbbec0b04f3eba5b9 Mon Sep 17 00:00:00 2001 From: Ricky Stewart <ricky@cockroachlabs.com> Date: Thu, 1 Aug 2024 17:25:33 -0500 Subject: [PATCH] bazel: never strip output binaries To date, binaries are stripped by default when building with Bazel. We skip stripping for release binaries (via `-c opt`) and if you're building with the `dev` configuration (many developers use this configuration as `dev doctor` guides you to). This has led to some confusion as these mechanisms are non-obvious, leading some to wonder why their binaries are (or are not) stripped. We simplify this by *never* stripping. Since release binaries are not stripped, they are unaffected by this change. Only developers building without the `dev` config and CI jobs that don't set `-c opt` would be affected. Epic: CRDB-17171 Release note: None --- .bazelrc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.bazelrc b/.bazelrc index 1b9a7d0ac0c4..9fcff95a6b0a 100644 --- a/.bazelrc +++ b/.bazelrc @@ -47,7 +47,7 @@ build --define gotags=bazel,gss build --experimental_proto_descriptor_sets_include_source_info build --incompatible_strict_action_env --incompatible_enable_cc_toolchain_resolution build --symlink_prefix=_bazel/ -build:dev --strip=never +build --strip=never common --experimental_allow_tags_propagation test --config=test --experimental_ui_max_stdouterr_bytes=10485760 build --ui_event_filters=-DEBUG