mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <>
Cc:, Trent Piepho <>,
	Ahmad Fatoum <>
Subject: [PATCH v2 1/4] common: remove !SANDBOX dependency for target tools
Date: Fri, 17 Sep 2021 19:41:24 +0200	[thread overview]
Message-ID: <> (raw)

d4aa01503348 ("common: add dependency !SANDBOX on target tools") and
later commits disabled building the target tools with sandbox, because
the build failed when they were enabled.

This has been fixed since then. Remove the limitation, so target tools
can be cross-compiled when using the ARCH=sandbox.

Signed-off-by: Ahmad Fatoum <>
v1 -> v2:
  - no change
 common/Kconfig | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/common/Kconfig b/common/Kconfig
index a9feae2ae866..222a438ee545 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -740,7 +740,6 @@ config IMD_TARGET
-	depends on !SANDBOX
 	prompt "Build kernel-install utility for the target"
 	  Enable this to compile the kernel-install script using the cross
@@ -983,7 +982,6 @@ config DEFAULT_ENVIRONMENT_PATH
-	depends on !SANDBOX
 	prompt "build bareboxenv tool for target"
 	  'bareboxenv' is a tool to access the barebox environment from a running Linux
@@ -992,7 +990,6 @@ config BAREBOXENV_TARGET
 	prompt "build bareboxcrc32 tool for target"
-	depends on !SANDBOX
 	  'bareboxcrc32' is a userspacetool to generate the crc32 checksums the same way
 	  barebox does. Say yes here to build it for the target.

barebox mailing list

             reply	other threads:[~2021-09-17 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 17:41 Ahmad Fatoum [this message]
2021-09-17 17:41 ` [PATCH v2 2/4] common: add new menu " Ahmad Fatoum
2021-09-17 17:41 ` [PATCH v2 3/4] scripts: omap3-usb-loader: make proper use of pkg-config --cflags Ahmad Fatoum
2021-09-17 17:41 ` [PATCH v2 4/4] scripts: allow building USB loader tools for target as well Ahmad Fatoum
2021-10-02  9:13 ` [PATCH v2 1/4] common: remove !SANDBOX dependency for target tools Sascha Hauer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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