Describe the issue
Currently, the documented method of printing values via AbslStringify only works if you set -DGTEST_HAS_ABSL. However, when using googletest from the BCR, this dependency is unconditional yet the define still defaults to off, pulling in the dependency but not actually using it.
Steps to reproduce the problem
- Add
bazel_dep(name = "googletest", version = "1.17.0.bcr.2") to MODULE.bazel
- Define a custom
AbslStringify for a type.
- Have a test fail using that type.
- Be surprised when the wrong value is printed or compilation fails (depending on the type).
What version of GoogleTest are you using?
googletest-1.17.0.bcr.2
What operating system and version are you using?
macos 25.3.0
What compiler and version are you using?
clang 19.1.3
What build system are you using?
bazel 9.0.0
Additional context
No response
Describe the issue
Currently, the documented method of printing values via
AbslStringifyonly works if you set-DGTEST_HAS_ABSL. However, when using googletest from the BCR, this dependency is unconditional yet the define still defaults to off, pulling in the dependency but not actually using it.Steps to reproduce the problem
bazel_dep(name = "googletest", version = "1.17.0.bcr.2")toMODULE.bazelAbslStringifyfor a type.What version of GoogleTest are you using?
googletest-1.17.0.bcr.2
What operating system and version are you using?
macos 25.3.0
What compiler and version are you using?
clang 19.1.3
What build system are you using?
bazel 9.0.0
Additional context
No response