Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Compagnucci <angelo@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 02/10] package/go: refactor host/target dependencies
Date: Tue,  5 Feb 2019 17:00:28 +0100	[thread overview]
Message-ID: <1549382436-15177-3-git-send-email-angelo@amarulasolutions.com> (raw)
In-Reply-To: <1549382436-15177-1-git-send-email-angelo@amarulasolutions.com>

In order to better handling the host/target dependencies of packages, we
need to add the new configuration option BR2_PACKAGE_HOST_GO_TARGET_SUPPORTS.
All golang target packages should depends on this options.
Host packages needs to depend instead on the already available
BR2_PACKAGE_HOST_GO_BOOTSTRAP_ARCH_SUPPORTS.

Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
---
 package/go/Config.in.host | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/package/go/Config.in.host b/package/go/Config.in.host
index f619ca0..508f664 100644
--- a/package/go/Config.in.host
+++ b/package/go/Config.in.host
@@ -1,4 +1,4 @@
-config BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS
+config BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
 	bool
 	default y
 	depends on !BR2_TOOLCHAIN_HAS_BINUTILS_BUG_20006
@@ -10,10 +10,16 @@ config BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS
 	# MIPS R6 support in Go has not yet been developed.
 	depends on !BR2_MIPS_CPU_MIPS64R6
 
-config BR2_PACKAGE_HOST_GO_CGO_LINKING_SUPPORTS
+config BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
 	bool
 	default y
-	depends on BR2_PACKAGE_HOST_GO_ARCH_SUPPORTS
+	depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
 	# Go doesn't support CGO linking on MIPS64x platforms
 	# See: https://github.com/karalabe/xgo/issues/46
 	depends on !BR2_mips64 && !BR2_mips64el
+
+config BR2_PACKAGE_HOST_GO_TARGET_SUPPORTS
+	bool
+	default y
+	depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
+	depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
-- 
2.7.4

  parent reply	other threads:[~2019-02-05 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 16:00 [Buildroot] [PATCH v2 00/10] Adding mender-artifact Angelo Compagnucci
2019-02-05 16:00 ` [Buildroot] [PATCH v2 01/10] package/pkg-golang: add support for building host packages Angelo Compagnucci
2019-02-05 16:00 ` Angelo Compagnucci [this message]
2019-02-05 16:00 ` [Buildroot] [PATCH v2 03/10] package/docker-cli: using BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS Angelo Compagnucci
2019-02-05 16:00 ` [Buildroot] [PATCH v2 04/10] package/docker-containerd: " Angelo Compagnucci
2019-02-05 16:00 ` [Buildroot] [PATCH v2 05/10] package/docker-engine: " Angelo Compagnucci
2019-02-05 16:00 ` [Buildroot] [PATCH v2 06/10] package/docker-proxy: " Angelo Compagnucci
2019-02-05 16:00 ` [Buildroot] [PATCH v2 07/10] package/flannel: " Angelo Compagnucci
2019-02-05 16:00 ` [Buildroot] [PATCH v2 08/10] package/mender: " Angelo Compagnucci
2019-02-05 16:00 ` [Buildroot] [PATCH v2 09/10] package/runc: " Angelo Compagnucci
2019-02-05 16:00 ` [Buildroot] [PATCH v2 10/10] package/mender-artifact: new package Angelo Compagnucci
2019-02-06  9:35   ` Thomas Petazzoni
2019-02-06 13:27     ` Angelo Compagnucci
2019-02-06  9:35 ` [Buildroot] [PATCH v2 00/10] Adding mender-artifact Thomas Petazzoni

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=1549382436-15177-3-git-send-email-angelo@amarulasolutions.com \
    --to=angelo@amarulasolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox