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
The binary produced from downloading the source of a tagged release, then 'make build'ing it doest get a version number or commit hash.
$ make build
fatal: Not a git repository (or any of the parent directories): .git
go get -d ./cmd/micro
go build -ldflags "-s -w -X main.Version=0.0.0-unknown -X main.CommitHash= -X 'main.CompileDate=June 22, 2017' " ./cmd/micro
Specifications
You can use micro -version to get the commit hash.
Commit hash:
OS: void linux
Terminal: xiate
The text was updated successfully, but these errors were encountered:
If you are getting the source from Source code (tar.gz) then it does not include the git repo info so you can not get a version or hash from it, with out hard coding version info in the Makefile yourself.
You have to use the micro-1.2.0-src.tar.gz to get version and hash from the git repo. There is a tag fault on v1.2.0 at the minute but hopfully it will be updated soon.
@tommyshem is correct. If you are getting the source from Github's build in Source code tar.gz, then it will be provided without the .git directory so micro will be unable to get the version from the git history.
You should use the micro-version-src.tar.gz instead which will provide the .git directory (as well as all dependencies and their .git directories -- which explains for the huge size).
I stopped providing the micro-version-src.tar.gz for a limited time, and it was also slightly bugged before (as you pointed out in #713). Please see my response their for the new situation.
Description of the problem or steps to reproduce
The binary produced from downloading the source of a tagged release, then 'make build'ing it doest get a version number or commit hash.
Specifications
You can use
micro -version
to get the commit hash.Commit hash:
OS: void linux
Terminal: xiate
The text was updated successfully, but these errors were encountered: