build.sh on windows is not creating binary where it should

Question

build.sh on windows is not creating binary where it should

Closed this issue 4 years ago · 4 comments

sjanc commented 5 years ago

newt binary is left in /tmp folder which deleted at then end of script...

There seems to be some subtle change in go 1.12 about how it handles paths..

Answer 1 · 2019-07-17T12:34:31.000Z

If just run go build on newt path does it work?

Answer 2 · 2019-09-25T12:46:04.000Z

yeap, it works just fine and binary is in folder I executed 'go build'.
I suspect build.sh magic with tmp godir etc is causing issues...

Answer 3 · 2020-03-26T11:34:16.000Z

ok, the issue was not running msys2 shell as administrator (which prevented symlinks from working). Closing.

Answer 4 · 2020-09-28T20:47:23.000Z

Hi @sjanc,

Running the msys2 shell as administrator didn't work for me on Windows 10 system.

For those trying to build newt from source before running ./build.sh open the file and comment out rm -rf "$godir"

Run ./build.sh
Go to your msys2 install directory and look inside the /tmp folder. You will find the newt build directory and then navigate to /newt and you will find the newt.exe file.