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
It seems this is unmaintained but figured I'd raise this anyway.
A reason I usually go build -o app.exe ; ./app.exe is to keep security software from treating each compilation as a new binary (because it uses a temporary directory). Otherwise, if the application wants access to certain resources such as network sockets, webcams, sound, etc. then you must hit "allow access" for every compilation.
I went to try this app, and it seems it also uses a different output name for every compilation. Resulting in this:
It also doesn't seem to clean up these temporary binaries, which has resulted in my %userprofile%/go/bin directory filling up with executables named watcher-.-(random ID).
The text was updated successfully, but these errors were encountered:
It seems this is unmaintained but figured I'd raise this anyway.
A reason I usually
go build -o app.exe ; ./app.exe
is to keep security software from treating each compilation as a new binary (because it uses a temporary directory). Otherwise, if the application wants access to certain resources such as network sockets, webcams, sound, etc. then you must hit "allow access" for every compilation.I went to try this app, and it seems it also uses a different output name for every compilation. Resulting in this:
It also doesn't seem to clean up these temporary binaries, which has resulted in my %userprofile%/go/bin directory filling up with executables named
watcher-.-(random ID)
.The text was updated successfully, but these errors were encountered: