fix: remove dev_dependency flag from google_benchmark#163
fix: remove dev_dependency flag from google_benchmark#163AlexanderLanin wants to merge 1 commit intoeclipse-score:mainfrom
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
There was a problem hiding this comment.
Pull Request Overview
This PR removes the dev_dependency = True flag from the google_benchmark dependency, converting it from a development-only dependency to a regular dependency in the build system.
Key Changes
- Changed
google_benchmarkfrom a dev dependency to a production dependency in MODULE.bazel
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| bazel_dep(name = "googletest", version = "1.17.0.bcr.1") | ||
|
|
||
| bazel_dep(name = "google_benchmark", version = "1.9.4", dev_dependency = True) | ||
| bazel_dep(name = "google_benchmark", version = "1.9.4") |
There was a problem hiding this comment.
The google_benchmark dependency should include dev_dependency = True since it's only used for benchmarking tests (see src/cpp/tests/bm_kvs.cpp). This follows the same pattern as other test-only dependencies in this file like googletest, rules_python, rust, and score_toolchains_gcc. Without this flag, the benchmark library will be included in production builds unnecessarily, potentially increasing build times and binary sizes.
| bazel_dep(name = "google_benchmark", version = "1.9.4") | |
| bazel_dep(name = "google_benchmark", version = "1.9.4", dev_dependency = True) |
|
The created documentation from the pull request is available at: docu-html |
google_benchmark cannot be a dev_dependency. Rules for dev_dependency still not understood.... but we need this fix in reference_integration, otherwise it does not work at all.