diff options
Diffstat (limited to 'docs/buildroot.html')
| -rw-r--r-- | docs/buildroot.html | 39 |
1 files changed, 27 insertions, 12 deletions
diff --git a/docs/buildroot.html b/docs/buildroot.html index 6d4f17c75..fc754e581 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -171,7 +171,7 @@ or <p>All of these "make" commands will need to build a configuration utility, so you may need to install "development" packages for - relevent libraries used by the configuration utilities. + relevant libraries used by the configuration utilities. On Debian-like systems, the <code>libncurses5-dev</code> package is required to use the <i>menuconfig</i> interface, <code>libqt3-mt-dev</code> is @@ -260,7 +260,7 @@ or <p>If you intend to do an offline build and just want to download all sources that you previously selected in the configurator - (<i>menuconfig</i> or <i>xconfig</i>), then issue:</p> + (<i>menuconfig</i>, <i>xconfig</i> or <i>gconfig</i>), then issue:</p> <pre> $ make source </pre> @@ -278,20 +278,35 @@ or $ make O=/tmp/build </pre> + <p>Or:</p> + +<pre> + $ cd /tmp/build; make O=$PWD -C path/to/buildroot +</pre> + <p>All the output files will be located under <code>/tmp/build</code>.</p> <p>When using out-of-tree builds, the Buildroot - <code>.config</code> and temporary files are also stored in the + <code>.config</code> and temporary files are also stored in the output directory. This means that you can safely run multiple builds in parallel using the same source tree as long as they use unique output directories.</p> + <p>For ease of use, Buildroot generates a Makefile wrapper in the + output directory - So after the first run, you no longer need to + pass <code>O=..</code> and <code>-C ..</code>, simply run (in the + output directory):</p> + +<pre> + $ make <target> +</pre> + <h3><a name="environment_variables" id="environment_variables"></a> Environment variables</h3> <p>Buildroot also honors some environment variables when they are passed - to <code>make</code>:</p> + to <code>make</code> or set in the environment:</p> <ul> <li><code>HOSTCXX</code>, the host C++ compiler to use</li> <li><code>HOSTCC</code>, the host C compiler to use</li> @@ -330,7 +345,7 @@ $ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD toolchain and tools, these changes will be lost. </li> <li>Customize the target filesystem skeleton available under - <code>target/generic/target_skeleton/</code>. You can customize + <code>fs/skeleton/</code>. You can customize configuration files or other stuff here. However, the full file hierarchy is not yet present because it's created during the compilation process. Therefore, you can't do everything on this target filesystem skeleton, but @@ -471,12 +486,12 @@ $ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD and which steps remain to be done, Buildroot maintains stamp files (empty files that just tell whether this or that action has been done). The problem is that these stamp files are not - uniformely named and handled by the different packages, so some + uniformly named and handled by the different packages, so some understanding of the particular package is needed.</p> <p>For packages relying on Buildroot packages infrastructures (see <a href="#add_packages">this section</a> for details), the - following stamp files are relevent:</p> + following stamp files are relevant:</p> <ul> @@ -689,7 +704,7 @@ endif <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 - environnement variable and then to use + environment variable and then to use <code>ARCH-linux-gcc</code>, <code>ARCH-linux-objdump</code>, <code>ARCH-linux-ld</code>, etc. </p> @@ -870,7 +885,7 @@ source "package/libfoo/Config.in" href="#generic-reference">reference</a>.</li> <li>Makefiles for autotools-based (autoconf, automake, etc.) - softwares. We provide a dedicated infrastructure for such + software. We provide a dedicated infrastructure for such packages, since autotools is a very common build system. This infrastructure <i>must</i> be used for new packages that rely on the autotools as their build system.<br/>We cover them through a @@ -1599,8 +1614,8 @@ LIBFOO_POST_PATCH_HOOKS += LIBFOO_POST_PATCH_FIXUP gettext library should not be compiled, because it creates various kind of build failures.</p> - <p>Additionnaly, some packages (such as libglib2) do require - gettext unconditionnally, while other packages (those who + <p>Additionally, some packages (such as libglib2) do require + gettext unconditionally, while other packages (those who support <code>--disable-nls</code> in general) only require gettext when locale support is enabled.</p> @@ -1616,7 +1631,7 @@ LIBFOO_POST_PATCH_HOOKS += LIBFOO_POST_PATCH_FIXUP </ul> - <p>Therefore, packages that unconditionnally need gettext should:</p> + <p>Therefore, packages that unconditionally need gettext should:</p> <ol> <li>Use <code>select BR2_PACKAGE_GETTEXT if |