If I compile this program
package main
import (
"fmt"
"os"
)
var version = os.Getenv("VERSION")
func main() {
fmt.Println(version)
}
It prints the env var when I run it
VERSION="0.123" ./example
> 0.123
Is there a way to compile the env var into the binary, for example:
VERSION="0.123" go build example.go
Then get the same output when I run
./example
Go 1.5 and above edit:
As of now, the syntax has changed.
On Unix use:
go build -ldflags "-X main.Version=$VERSION"
On Windows use:
go build -ldflags "-X main.Version=%VERSION%"
This is what -X linker flag is for. In your case, you would do
go build -ldflags "-X main.Version $VERSION"
Edit: on Windows this would be
go build -ldflags "-X main.Version %VERSION%"
go build -ldflags "-X main.Version %VERSION%"
link: warning: option -X main.Version 0.2 may not work in future releases; use -X main.Version=0.2. Also, I want to point out that you can set a default value when the env variable is not passed in, set var Version = 0.1 in example.go-ldflags "-X a=1 -X b=2".-ldflags "-X main.test=Hello" with a declared var test string is doing anything. When I run my program as an .exe on windows I also log the test variable to a .txt file to see if it works, but ´test` variable is just an empty stringAiner-G's answer led me to the right place, but it wasn't a full code sample answering the question. A couple of changes were required:
var version string-X main.version=$VERSIONHere's the full code:
package main
import (
"fmt"
)
var version string
func main() {
fmt.Println(version)
}
Now compile with
go build -ldflags "-X main.version=$VERSION"
go build behaves different to go run?
var date string, then compile with -ldflags "-X main.version=$VERSION -X main.date=$DATE"There is an os.Setenv() function which you can use to set environment variables.
So you can start your application by setting the environment variable like this:
func init() {
os.Setenv("VERSION", "0.123")
}
If you don't want to do this by "hand", you could create a tool for this which would read the current value of the VERSION environment variable and generate a .go source file in your package containing exactly like the code above (except using the current value of the VERSION environment variable). You can run such code generation by issuing the go generate command.
Read the Generating code blog post for more details about go generate.