Index: docs/buildroot-documentation.html =================================================================== RCS file: /var/cvs/buildroot/docs/buildroot-documentation.html,v retrieving revision 1.1 diff -u -u -r1.1 buildroot-documentation.html --- docs/buildroot-documentation.html 27 Dec 2004 19:01:52 -0000 1.1 +++ docs/buildroot-documentation.html 28 Dec 2004 19:02:31 -0000 @@ -18,7 +18,7 @@
Usage and documentation by Thomas Petazzoni. Contributions from Karsten Kruse, Ned Ludd, Martin Herren.
-Last modification : $Date: 2004-12-16 15:43:06 +0100 (Thu, 16 Dec 2004) $
+Last modification : $Id$
toolchain/uClibc/uClibc.config-locale
. The former
is used if you haven't selected locale support in Buildroot
configuration, and the latter is used if you have selected
- locale support.
+ locale support.
You may want to compile your own programs or other softwares + that are not packaged in Buildroot. In order to do this, you can + use the toolchain that was generated by Buildroot.
+ +The toolchain generated by Buildroot is located in
+ build_ARCH/staging_dir/
. The simplest way to use it
+ is to add build_ARCH/staging_dir/bin/
to your PATH
+ environnement variable, and then to use
+ arch-linux-gcc
, arch-linux-objdump
,
+ arch-linux-ld
, etc.
For example, you may add the following to your
+ .bashrc
(considering you're building for the MIPS
+ architecture and that Buildroot is located in
+ ~/buildroot/
) :
+export PATH=$PATH:~/buildroot/build_mips/bin/ ++ +
Then you can simply do :
+ ++mips-linux-gcc -o foo foo.c ++ +
Important : do not try to move the toolchain to an other + directory, it won't work. There are some hard-coded paths in the + gcc configuration. If the default toolchain directory + doesn't suit your needs, please refer to the Using the uClibc toolchain outside of + buildroot section.
+By default, the cross-compilation toolchain is generated inside
build_ARCH/staging_dir/
. But sometimes, it may be useful to
@@ -412,7 +449,7 @@
fact, the name of the software is the the identifier of the target
inside the real Makefile that will do everything (download,
compile, install), and that we study below. Back to
- Makefile.in
, here is an example :
+ Makefile.in
, here is an example :
ifeq ($(strip $(BR2_PACKAGE_FOO)),y)