From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/next] package/go: drop GO_TARGET_ENV / GO_HOST_ENV
Date: Sat, 29 Aug 2020 14:35:49 +0200 [thread overview]
Message-ID: <20200829124232.C3EE28152D@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=0d26fb58b79c6412c49287923e562ea6c8d950e0
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/next
Now that GO_TARGET_ENV and GO_HOST_ENV are just aliases to
HOST_GO_TARGET_ENV and HOST_GO_HOST_ENV, drop the former two, and use
the latter two directly.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
package/pkg-golang.mk | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/package/pkg-golang.mk b/package/pkg-golang.mk
index 9904ddcc1a..7424c31924 100644
--- a/package/pkg-golang.mk
+++ b/package/pkg-golang.mk
@@ -23,12 +23,6 @@
GO_BIN = $(HOST_DIR)/bin/go
-GO_TARGET_ENV = \
- $(HOST_GO_TARGET_ENV)
-
-GO_HOST_ENV = \
- $(HOST_GO_HOST_ENV)
-
################################################################################
# inner-golang-package -- defines how the configuration, compilation and
# installation of a Go package should be done, implements a few hooks to tune
@@ -102,7 +96,7 @@ endif
define $(2)_BUILD_CMDS
$$(foreach d,$$($(2)_BUILD_TARGETS),\
cd $$($(2)_SRC_PATH); \
- $$(GO_TARGET_ENV) \
+ $$(HOST_GO_TARGET_ENV) \
GOPATH="$$(@D)/$$($(2)_WORKSPACE)" \
$$($(2)_GO_ENV) \
$$(GO_BIN) build -v $$($(2)_BUILD_OPTS) \
@@ -115,7 +109,7 @@ else
define $(2)_BUILD_CMDS
$$(foreach d,$$($(2)_BUILD_TARGETS),\
cd $$($(2)_SRC_PATH); \
- $$(GO_HOST_ENV) \
+ $$(HOST_GO_HOST_ENV) \
GOPATH="$$(@D)/$$($(2)_WORKSPACE)" \
$$($(2)_GO_ENV) \
$$(GO_BIN) build -v $$($(2)_BUILD_OPTS) \
reply other threads:[~2020-08-29 12:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200829124232.C3EE28152D@busybox.osuosl.org \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.