Lol you have to setup the necessary build directories bin,src,etc and environment variables before using golang from tarball e.g. GOROOT, GOPATH, GOPROXY=direct or you’re gonna run into issues. Golang is easily the most overcomplicated when it comes to setup the of the dev environment.
It wasn't always like this, in the early days you only needed GOROOT and GOPATH. Nowadays there are numerous hidden envvar toggles like GOPROXY and GOMODULES111.
Even still, this doesn't seem more difficult than installing and learning how to use ninja and / or meson build.
It's only two commands, clearly stated in the docs. No configuration required.
meson setup build
ninja -C build
It's not like meson or ninja is an obscure tool either, contrary to what this thread suggests. They're both popular C/C++ build tools along with cmake.
Comments
Lol you have to setup the necessary build directories bin,src,etc and environment variables before using golang from tarball e.g. GOROOT, GOPATH, GOPROXY=direct or you’re gonna run into issues. Golang is easily the most overcomplicated when it comes to setup the of the dev environment.
It wasn't always like this, in the early days you only needed GOROOT and GOPATH. Nowadays there are numerous hidden envvar toggles like GOPROXY and GOMODULES111.
Even still, this doesn't seem more difficult than installing and learning how to use ninja and / or meson build.
It's only two commands, clearly stated in the docs. No configuration required.
It's not like meson or ninja is an obscure tool either, contrary to what this thread suggests. They're both popular C/C++ build tools along with cmake.True.