e4fdb42496
As noticed by @riking, the logic in the bash script will break when Go 1 version numbers reach double-digits. Instead, use a build tag "!go1.5" to cause a syntax error: $ /opt/go1.4.3/bin/go build can't load package: package github.com/rfjakob/gocryptfs: go1.4.go:5:1: expected 'package', found 'STRING' "You need Go 1.5 or higher to compile gocryptfs!" Fixes https://github.com/rfjakob/gocryptfs/issues/133
42 lines
962 B
Bash
Executable File
42 lines
962 B
Bash
Executable File
#!/bin/bash
|
|
|
|
set -eu
|
|
|
|
cd "$(dirname "$0")"
|
|
MYDIR=$PWD
|
|
|
|
# GOPATH may contain multiple paths separated by ":"
|
|
GOPATH1=$(go env GOPATH | cut -f1 -d:)
|
|
|
|
# gocryptfs version according to git
|
|
GITVERSION=$(git describe --tags --dirty)
|
|
|
|
# go-fuse version according to git
|
|
# Note: git in CentOS 7 does not have "git -C" yet, so we use plain "cd".
|
|
FAIL=0
|
|
cd $GOPATH1/src/github.com/hanwen/go-fuse
|
|
OUT=$(git describe --tags --dirty 2>&1) || FAIL=1
|
|
if [[ $FAIL -ne 0 ]]; then
|
|
echo "$PWD: git describe: $OUT"
|
|
echo "Hint: are you missing git tags?"
|
|
exit 1
|
|
fi
|
|
GITVERSIONFUSE=$OUT
|
|
cd "$MYDIR"
|
|
|
|
# Build Unix timestamp, something like 1467554204.
|
|
BUILDTIME=$(date +%s)
|
|
|
|
# Make sure we have the go binary
|
|
go version > /dev/null
|
|
|
|
LDFLAGS="-X main.GitVersion=$GITVERSION -X main.GitVersionFuse=$GITVERSIONFUSE -X main.BuildTime=$BUILDTIME"
|
|
go build "-ldflags=$LDFLAGS" $@
|
|
|
|
(cd gocryptfs-xray; go build $@)
|
|
|
|
./gocryptfs -version
|
|
|
|
mkdir -p $GOPATH1/bin
|
|
cp -af gocryptfs $GOPATH1/bin
|