From: Jose Quaresma <quaresma.jose@gmail.com>
Date: Thu, 7 Mar 2024 10:06:59 +0000 (-0800)
Subject: go.bbclass: set GOPROXY
X-Git-Tag: 2024-04-scarthgap~175
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e0919a3f7bc26b1ea9fb57740de4a9a3b9253f26;p=thirdparty%2Fopenembedded%2Fopenembedded-core.git

go.bbclass: set GOPROXY

The GOPROXY is already correctly defined on the native sys root
and this can be checked using the bitbake devshell:

| $ go env GOPROXY
| https://proxy.golang.org,direct

The go_do_compile task calls the compiler directly so the
GOPROXY env is not seen because it's not defined in the shell.
Defining it explicitly solves this problem and was to avoid
setting it in the recipes itself.

Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---

diff --git a/meta/classes-recipe/go.bbclass b/meta/classes-recipe/go.bbclass
index 39bfaa51568..cc3564c36a9 100644
--- a/meta/classes-recipe/go.bbclass
+++ b/meta/classes-recipe/go.bbclass
@@ -78,6 +78,7 @@ GO_INSTALL_FILTEROUT ?= "${GO_IMPORT}/vendor/"
 B = "${WORKDIR}/build"
 export GOPATH = "${B}"
 export GOENV = "off"
+export GOPROXY ??= "https://proxy.golang.org,direct"
 export GOTMPDIR ?= "${WORKDIR}/build-tmp"
 GOTMPDIR[vardepvalue] = ""