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
Hey Gophers, I have a proposal for a more flexible build environment:
If I run go get or go build then would it be great if it executes make if a Makefile exists in the current directory. It could also work via a configuration flag:
go build --backend=make
Furthermore it would be good to use such options via a configuration file (like a Go.toml inside the main directory, our Rust brothers already do this), to tell the compiler to apply package specific settings during a simple execution of go build.
This has the benefit that I can create more flexible build environments, like downloading artifacts from certain place during the build. What do you think?
The text was updated successfully, but these errors were encountered:
This would not be portable (won't work on Windows), won't work if you don't have the tools in general, and means a "go get" suddenly can run arbitrary code on your machine, which has never been the case before.
Hey Gophers, I have a proposal for a more flexible build environment:
If I run
go get
orgo build
then would it be great if it executesmake
if aMakefile
exists in the current directory. It could also work via a configuration flag:Furthermore it would be good to use such options via a configuration file (like a
Go.toml
inside the main directory, our Rust brothers already do this), to tell the compiler to apply package specific settings during a simple execution ofgo build
.This has the benefit that I can create more flexible build environments, like downloading artifacts from certain place during the build. What do you think?
The text was updated successfully, but these errors were encountered: