Skip to contentSkip to conversation

toolchain: introduce HOST_DIR option

PATCH New Gustavo Zacarias 3 participants 6 messages Feb 2, 2011 Kbuild

lore
Share & tools
lore

Gustavo Zacarias

author
#0 lore raw

PATCH 1/2 toolchain: introduce HOST_DIR option

Allow the user to define HOST_DIR in the config menu.

This way when building an internal toolchain a separate (maybe shared) output directory may be defined and the toolchain can be used by multiple users and/or projects.

Signed-off-by Gustavo Zacarias <[email protected]>
---
 Config.in |   10 ++++++++++
 Makefile  |    4 ++--
 2 files changed, 12 insertions(+), 2 deletions(-)
Config.in +10 -0
index df0c7ce..af44b89 100644
@@ -72,6 +72,16 @@ config BR2_DL_DIR
 
 	  The default is $(TOPDIR)/dl
 
+config BR2_HOST_DIR
+	string "Host dir"
+	default "$(BASE_DIR)/host"
+	help
+	  Directory to store all the binary files that are built for the host.
+	  This includes the cross compilation toolchain when building the
+	  internal buildroot toolchain.
+
+	  The default is $(BASE_DIR)/host
+
 menu "Mirrors and Download locations"
 
 config BR2_PRIMARY_SITE
Makefile +2 -2
index 3ecc597..7bd49f4 100644
@@ -274,8 +274,8 @@ TAR_OPTIONS=$(call qstrip,$(BR2_TAR_OPTIONS)) -xf
 
 GNU_TARGET_SUFFIX:=-$(call qstrip,$(BR2_GNU_TARGET_SUFFIX))
 
-# packages compiled for the host goes here
-HOST_DIR:=$(BASE_DIR)/host
+# packages compiled for the host go here
+HOST_DIR:=$(call qstrip,$(BR2_HOST_DIR))
 
 # stamp (dependency) files go here
 STAMP_DIR:=$(BASE_DIR)/stamps
Signature · 1 line
1.7.3.4
author
#1 lore raw

PATCH 2/2 documentation: update buildroot internal toolchain usage

Signed-off-by Gustavo Zacarias <[email protected]>
---
 docs/buildroot.html |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
docs/buildroot.html +4 -4
index 36297e0..b755922 100644
@@ -618,8 +618,8 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured
     use the toolchain that was generated by Buildroot.</p>
 
     <p>The toolchain generated by Buildroot is located by default in
-    <code>output/staging/</code>. The simplest way to use it is to add
-    <code>output/staging/usr/bin/</code> to your PATH environment variable and
+    <code>output/host/</code>. The simplest way to use it is to add
+    <code>output/host/usr/bin/</code> to your PATH environment variable and
     then to use <code>ARCH-linux-gcc</code>, <code>ARCH-linux-objdump</code>,
     <code>ARCH-linux-ld</code>, etc.</p>
 

@@ -628,8 +628,8 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured
     is called to tell where the libraries and header files are.</p>
 
     <p>It is also possible to generate the Buildroot toolchain in a
-    directory other than <code>output/staging</code> by using the <code>
-    Build options -&gt; Toolchain and header file location</code> options.
+    directory other than <code>output/host</code> by using the <code>
+    Build options -&gt; Host dir</code> option.
     This could be useful if the toolchain must be shared with other users.</p>
 
     <h2 id="ccache-support">Using <code>ccache</code> in Buildroot</h2>
Signature · 1 line
1.7.3.4
#4 lore raw

PATCH 1/2 toolchain: introduce HOST_DIR option

In reply to Gustavo Zacarias
Quoted 7 lines · On Wed, 2 Feb 2011 10:05:56 -0300 Gustavo Zacarias <[email protected]>…

Allow the user to define HOST_DIR in the config menu.

This way when building an internal toolchain a separate (maybe shared) output directory may be defined and the toolchain can be used by multiple users and/or projects.

Signed-off-by Gustavo Zacarias <[email protected]>
Acked-by Thomas Petazzoni <[email protected]>

Thanks,

Thomas

Signature · 4 lines
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
#5 lore raw

PATCH 1/2 toolchain: introduce HOST_DIR option

In reply to Gustavo Zacarias
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Gustavo" == Gustavo Zacarias <[email protected]> writes:

Gustavo> Allow the user to define HOST_DIR in the config menu. Gustavo> This way when building an internal toolchain a separate (maybe shared) Gustavo> output directory may be defined and the toolchain can be used by Gustavo> multiple users and/or projects.

Committed, thanks.

Signature · 1 line
Bye, Peter Korsgaard