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
$ garble version v0.7.2
$ go version go1.19 windows/amd64
What environment are you running Garble on?
go env Output
$ go env set GO111MODULE=on
set GOARCH=wasm
set GOBIN=
set GOCACHE=C:\Users\Daniel\AppData\Local\go-build
set GOENV=C:\Users\Daniel\AppData\Roaming\go\env
set GOEXE=
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\Daniel\Desktop\go-workspace\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=js
set GOPATH=C:\Users\Daniel\Desktop\go-workspace
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.19
set GCCGO=gccgo
set GOWASM=
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=0
set GOMOD=C:\Program Files\Go\src\kard\go.mod
set GOWORK=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-fPIC -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=C:\Users\Daniel\AppData\Local\Temp\go-build4175388778=/tmp/go-build -gno-record-gcc-switches
What did you do?
Ran the command set GOOS=js&& set GOARCH=wasm&& garble build -o C:\Users\Daniel\Desktop\go-workspace\src\sandbox\other\wasm\assets\json.wasm kard to compile the package kard in go/src/ to json.wasm in the specified folder.
What did you expect to see?
A compiled json.wasm in the assets folder. The same command using go build works as it should (set GOOS=js&& set GOARCH=wasm&& go build -o C:\Users\Daniel\Desktop\go-workspace\src\sandbox\other\wasm\assets\json.wasm kard)
Running the garble command within the directory itself functions as it should, however, as I'm using a compile daemon which means I need to compile the build from elsewhere, the above is necessary to be called outside of the package directory (like how it works with go build)
What did you see instead?
GOGARBLE="bot,bot_test" does not match any packages to be built
The text was updated successfully, but these errors were encountered:
See the README; GOGARBLE defaults to the current moduel path. You should try changing it to what you really want it to be, or something more agressive like GOGARBLE=*.
I'm going to guess that my answer above is enough. In the future, we'll move to a GOGARBLE default that is the same no matter what your current directory is, so that should be less confusing as well. See #594.
What version of Garble and Go are you using?
What environment are you running Garble on?
go env
OutputWhat did you do?
Ran the command
set GOOS=js&& set GOARCH=wasm&& garble build -o C:\Users\Daniel\Desktop\go-workspace\src\sandbox\other\wasm\assets\json.wasm kard
to compile the packagekard
in go/src/ to json.wasm in the specified folder.What did you expect to see?
A compiled json.wasm in the assets folder. The same command using go build works as it should (
set GOOS=js&& set GOARCH=wasm&& go build -o C:\Users\Daniel\Desktop\go-workspace\src\sandbox\other\wasm\assets\json.wasm kard
)Running the garble command within the directory itself functions as it should, however, as I'm using a compile daemon which means I need to compile the build from elsewhere, the above is necessary to be called outside of the package directory (like how it works with go build)
What did you see instead?
GOGARBLE="bot,bot_test" does not match any packages to be built
The text was updated successfully, but these errors were encountered: