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
Does this issue reproduce with the latest releases of all the above?
All of the above is the latest of releases at the time of writing this. (2022.07.27)
What operating system and processor architecture are you using?
Windows 10, 64-bit x86
What did you do?
I followed the Gazelle README setup for Bazel, then I ran the command bazel run //:gazelle in the root of a repo where I tried to set up Go and Node.js - although I got stuck with Go.
I encountered the same problem, the same Gin Hello World project, under Windows 11, but it was normal under WSL. Based on the prompt information, I guessed that it was a file extension issue.
grep: C:\\Users\\xxxx\\_bazel_xxxx\\jik7kwyi\\execroot\\__main__\\bazel-out\\x64_windows-fastbuild\\bin\\gazelle.runfiles_manifest: No such file or directory
C:\\Users\\xxxx\\_bazel_xxxx\\jik7kwyi\\execroot\\__main__\\bazel-out\\x64_windows-fastbuild\\bin\\gazelle: warning: could not locate GOROOT used by rules_go
grep: C:\\Users\\xxxx\\_bazel_xxxx\\jik7kwyi\\execroot\\__main__\\bazel-out\\x64_windows-fastbuild\\bin\\gazelle.runfiles_manifest: No such file or directory
error: could not locate gazelle binary
There is only the "gazelle. exe. runfiles_manifest" file in this folder, and there is no "gazelle. runfiles_manifest" file.
I suggest using this tool on Linux until it improves support for Windows.
Versions
0.26.0
0.34.0
5.2.0
Does this issue reproduce with the latest releases of all the above?
All of the above is the latest of releases at the time of writing this. (2022.07.27)
What operating system and processor architecture are you using?
Windows 10, 64-bit x86
What did you do?
I followed the Gazelle README setup for Bazel, then I ran the command
bazel run //:gazelle
in the root of a repo where I tried to set up Go and Node.js - although I got stuck with Go.My GitHub repo can be found here
What did you expect to see?
I expected Gazelle to create a BUILD.bazel file in the
go/services/core
.What did you see instead?
This was the command output:
The
bazel-*
folders are generated and there are these files in thebazel-out\x64_windows-fastbuild\bin
folder:gazelle
gazelle-runner.bash
gazelle.exe
gazelle.exe.runfiles_manifest
At the moment I'm not even sure I'm using Gazelle correctly, so any clarification is appreciated.
The text was updated successfully, but these errors were encountered: