$ bazel build //examples/cpp:hello-world --cpu=x64_windows_msys --compiler=windows_msys64 --glibc=local
ERROR: No toolchain found for --cpu='x64_windows' --compiler='windows_msys64' --glibc='local'. Valid toolchains are: [
--cpu='armeabi-v7a' --compiler='compiler' --glibc='armeabi-v7a',
--cpu='ios_x86_64' --compiler='compiler' --glibc='ios',
--cpu='x64_windows_msys' --compiler='windows_msys64' --glibc='local',
--cpu='x64_windows' --compiler='cl' --glibc='msvcrt140',
].
Is there a reason why the cpu arg gets automatically changed from x64_windows_msys to x64_windows? Fwiw, here is the version of bazel I am using
$ bazel version
.................
Build label: 0.7.0
Build target: bazel-out/msvc_x64-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Wed Oct 18 14:25:56 2017 (1508336756)
Build timestamp: 1508336756
Build timestamp as int: 1508336756
Thanks for your help.
--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/0a8a8915-b2db-422b-802a-9cf67d82d4ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.