1 To build and use the buildroot stuff, do the following:
3 1) run 'make menuconfig'
4 2) select the packages you wish to compile
6 4) wait while it compiles
7 5) Use your shiny new root filesystem. Depending on which sort of
8 root filesystem you selected, you may want to loop mount it,
9 chroot into it, nfs mount it on your target device, burn it
10 to flash, or whatever is appropriate for your target system.
12 You do not need to be root to build or run buildroot. Have fun!
17 In order to do an offline-build (not connected to the net), fetch all
18 selected source by issuing a
21 before you disconnect.
22 If your build-host is never connected, then you have to copy buildroot
23 and your toplevel .config to a machine that has an internet-connection
24 and issue "make source" there, then copy the content of your dl/ dir to
30 Buildroot supports building out of tree with a syntax similar
31 to the Linux kernel. To use it, add O=<directory> to the
32 make command line, E.G.:
36 And all the output files (including .config) will be located under /tmp/build.
38 More finegrained configuration:
39 ===============================
41 You can specify a config-file for uClibc:
42 $ make UCLIBC_CONFIG_FILE=/my/uClibc.config
44 And you can specify a config-file for busybox:
45 $ make BUSYBOX_CONFIG_FILE=/my/busybox.config
47 To use a non-standard host-compiler (if you do not have 'gcc'),
48 make sure that the compiler is in your PATH and that the library paths are
49 setup properly, if your compiler is built dynamically:
50 $ make HOSTCC=gcc-4.3.orig HOSTCXX=gcc-4.3-mine
52 Depending on your configuration, there are some targets you can use to
53 use menuconfig of certain packages. This includes:
54 $ make HOSTCC=gcc-4.3 linux-menuconfig
55 $ make HOSTCC=gcc-4.3 uclibc-menuconfig
56 $ make HOSTCC=gcc-4.3 busybox-menuconfig
58 Please feed suggestions, bug reports, insults, and bribes back to the
59 buildroot mailing list: buildroot@buildroot.org