diff options
| author | Abseil Team <absl-team@google.com> | 2024-12-23 21:32:38 (GMT) |
|---|---|---|
| committer | Copybara-Service <copybara-worker@google.com> | 2024-12-23 21:33:10 (GMT) |
| commit | e54519b09463cec3aea77a1739e02c97ca766da5 (patch) | |
| tree | f4b844c155953c0f344f65452041453c09f5564b /googletest/test/gtest_xml_output_unittest.py | |
| parent | f3c355f9dd382bc2c323be2713e351a578b68c61 (diff) | |
| download | googletest-e54519b09463cec3aea77a1739e02c97ca766da5.zip googletest-e54519b09463cec3aea77a1739e02c97ca766da5.tar.gz googletest-e54519b09463cec3aea77a1739e02c97ca766da5.tar.bz2 | |
Put the fake Fuchsia SDK in a module extension
This allows users to override the fake SDK with a real one using https://bazel.build/rules/lib/globals/module#override_repo.
Without this change, it is impossible for a project that depends on googletest as a `bazel_dep` to build tests using the "real" Fuchsia SDK, because any references to `@fuchsia_sdk` within googletest `BUILD.bazel` files unconditionally resolve to the "fake" Fuchsia SDK. With this change, if you have the real Fuchsia SDK declared in your `MODULE.bazel`, you can add the following lines to coerce googletest to use the real Fuchsia SDK as well:
fake_fuchsia_sdk_extension =
use_extension("@com_google_googletest//:fake_fuchsia_sdk.bzl", "fuchsia_sdk")
override_repo(fake_fuchsia_sdk_extension, "fuchsia_sdk")
PiperOrigin-RevId: 709139784
Change-Id: I4d10d441c76b7a2481f15723a24f11525dba3878
Diffstat (limited to 'googletest/test/gtest_xml_output_unittest.py')
0 files changed, 0 insertions, 0 deletions