Update make targets: (#1900)
* Update make targets: * `make dev` now shows a message indicating the new commands * `make build` builds the binary into bin/ * `make install` will subsequently `mv` (not copy) the binary into GOPATH/bin The reason for the `mv` is that M1 Macs seem to get pretty unhappy about executing a copied binary if it's been modified, so an initial binary is fine, then after changing and recompiling the command keeps getting killed. * Make the 'make install' text more clear
This commit is contained in:
1 parent
bc6689fb16
commit
b53e4d4c3e
2 files changed
+21
-9
No files matched your search
+6
-5
@@ -69,17 +69,18 @@ rm -f bin/*
|
||||
mkdir -p bin/
|
||||
|
||||
# Build!
|
||||
echo "==> Building..."
|
||||
echo "==> Building into bin/..."
|
||||
BINARY_NAME="boundary${BINARY_SUFFIX}"
|
||||
go build -tags="${BUILD_TAGS}" \
|
||||
-ldflags "-X github.com/hashicorp/boundary/version.GitCommit=${GIT_COMMIT}${GIT_DIRTY}" \
|
||||
-o "bin/${BINARY_NAME}" \
|
||||
./cmd/boundary
|
||||
|
||||
|
||||
# Copy binary into gopath
|
||||
echo "==> Copying binary into GOPATH"
|
||||
cp -f "bin/${BINARY_NAME}" "${GOPATH}/bin/"
|
||||
# Copy binary into gopath if desired
|
||||
if [ "${BOUNDARY_INSTALL_BINARY}x" != "x" ]; then
|
||||
echo "==> Moving binary into GOPATH/bin..."
|
||||
mv -f "bin/${BINARY_NAME}" "${GOPATH}/bin/"
|
||||
fi
|
||||
|
||||
# Done!
|
||||
echo "==> Done!"
|
||||
Reference in new issue
Block a user