summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2020-05-05 17:41:13 -0400
committerDaniel J Walsh <dwalsh@redhat.com>2020-05-07 16:47:56 -0400
commitb27aa5f81b6197817fcbc659019a65f50c8892b2 (patch)
treef9e9c8c18e7e3a05c64da5fa17bbc941f21ef751
parent1d3cdf9a4642df073becb54d178d6b1959526a47 (diff)
downloadpodman-b27aa5f81b6197817fcbc659019a65f50c8892b2.tar.gz
podman-b27aa5f81b6197817fcbc659019a65f50c8892b2.tar.bz2
podman-b27aa5f81b6197817fcbc659019a65f50c8892b2.zip
Add podman-remote-static target
We should not be building podman-remote with the BUILDTAGS, these only effect server side. CRC Group wants to use a static version of podman-remote in order to install the same podman-remote client on any Linux box. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
-rw-r--r--Makefile6
1 files changed, 5 insertions, 1 deletions
diff --git a/Makefile b/Makefile
index bce0f33a1..2bbae0a72 100644
--- a/Makefile
+++ b/Makefile
@@ -189,7 +189,11 @@ podman: bin/podman
.PHONY: bin/podman-remote
bin/podman-remote: .gopathok $(SOURCES) go.mod go.sum $(PODMAN_VARLINK_DEPENDENCIES) ## Build with podman on remote environment
- $(GO_BUILD) $(BUILDFLAGS) -gcflags '$(GCFLAGS)' -asmflags '$(ASMFLAGS)' -ldflags '$(LDFLAGS_PODMAN)' -tags "!ABISupport $(BUILDTAGS) remoteclient" -o $@ $(PROJECT)/cmd/podman
+ $(GO_BUILD) $(BUILDFLAGS) -gcflags '$(GCFLAGS)' -asmflags '$(ASMFLAGS)' -ldflags '$(LDFLAGS_PODMAN)' -tags "!ABISupport remoteclient" -o $@ $(PROJECT)/cmd/podman
+
+.PHONY: bin/podman-remote-static
+podman-remote-static: bin/podman-remote-static
+ CGO_ENABLED=0 $(GO_BUILD) $(BUILDFLAGS) -gcflags '$(GCFLAGS)' -asmflags '$(ASMFLAGS)' -ldflags '$(LDFLAGS_PODMAN_STATIC)' -tags "!ABISupport containers_image_openpgp remoteclient" -o bin/podman-remote-static $(PROJECT)/cmd/podman
.PHONY: podman-remote
podman-remote: bin/podman-remote