You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current quickstart guide for building with Bazel uses commit 6092810
With Bazel 6, there is a build failure with the following message:
Constraints from @bazel_tools//platforms have been removed. Please use
constraints from @platforms repository embedded in Bazel, or preferably
declare dependency on https://github.com/bazelbuild/platforms. See
https://github.com/bazelbuild/bazel/issues/8622 for details.
This is resolved with a more recent commit (e.g. HEAD).
Use a more recent commit of googletest that uses OS constraints
from @platforms//os:* instead of from @build_tools//platforms:*
See bazelbuild/bazel#8622
Necessary to fixgoogle#4096
Also need the fix for google#4098
@platforms//os:* instead of from @build_tools//platforms:*
See bazelbuild/bazel#8622
Necessary to fixgoogle#4096
Also need the fix for google#4098
PiperOrigin-RevId: 497182073
Change-Id: Ifd568b088d2f779755dd20264edfd5dad12ca9cc
kunitoki
pushed a commit
to kunitoki/googletest
that referenced
this issue
Nov 4, 2023
@platforms//os:* instead of from @build_tools//platforms:*
See bazelbuild/bazel#8622
Necessary to fixgoogle#4096
Also need the fix for google#4098
PiperOrigin-RevId: 497182073
Change-Id: Ifd568b088d2f779755dd20264edfd5dad12ca9cc
Describe the issue
The current quickstart guide for building with Bazel uses commit
6092810
With Bazel 6, there is a build failure with the following message:
This is resolved with a more recent commit (e.g. HEAD).
Steps to reproduce the problem
Copy the directions in https://github.com/google/googletest/blob/main/docs/quickstart-bazel.md
What version of GoogleTest are you using?
6092810
What operating system and version are you using?
ubuntu 20.04
What compiler and version are you using?
gcc 9
What build system are you using?
Bazel 6.0.0
Additional context
No response
The text was updated successfully, but these errors were encountered: