a85c452a2d
XBMC is an award-winning free and open source (GPL) software media player and entertainment hub for digital media. We do provide a sub-option for each major feature we support, to avoid letting the user hunt-down required libraries, since the dependency is not always obvious and straightforward. We also provide our own wrapper script, because the ones bundled in XBMC are not suitable to all platforms. We need such a wrapper script because XBMC exits with different exit codes, depending on how the user quit XBMC: 0 is normal exit, 64 is for halt, and 66 is for reboot. So we can't simply call the real XBMC binary from the startup script, or we would lose this information. So, we provide a wrapper script that takes appropriate action according to the above exit codes. When run as root from a startup script, there is no HOME set, so XBMC defaults to saving its configuration in /.xbmc (yes, at the root of the rootfs). Since this does not play well with read-only filesystems (and is inherently ugly anyway), and sicne there is no real clean way to tell XBMC where to store its configuration, just provide a symlink to a better place: /.xbmc -> /var/xbmc (note: the only location _guaranteed_ to be writable is /tmp, but we want the configuration to survive a reboot. So, /var/xbmc looks a better place than /var/run/xbmc. and the user will have to take action to ensure /var/xbmc be writable.) (note: for this reason, we do not want to set $HOME to /root either, even if it is root running XBMC.) Some of XBMC sub-options select libraries that depend on toolchain options, such as IPv6. But those are already covered, being also implicit dependencies of XBMC, as XBMC can only be used on an (e)glibc toolchain anyway. When^WIf XBMC is one day buildable under uClibc/musl, this will be time to revisit those dependencies. This package was originally found at : https://github.com/huceke/buildroot-rbp By gimli <ebsi4711@gmail.com> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: gimli <ebsi4711@gmail.com> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| .defconfig | ||
| .gitignore | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
To build and use the buildroot stuff, do the following:
1) run 'make menuconfig'
2) select the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) Use your shiny new root filesystem. Depending on which sort of
root filesystem you selected, you may want to loop mount it,
chroot into it, nfs mount it on your target device, burn it
to flash, or whatever is appropriate for your target system.
You do not need to be root to build or run buildroot. Have fun!
Offline build:
==============
In order to do an offline-build (not connected to the net), fetch all
selected source by issuing a
$ make source
before you disconnect.
If your build-host is never connected, then you have to copy buildroot
and your toplevel .config to a machine that has an internet-connection
and issue "make source" there, then copy the content of your dl/ dir to
the build-host.
Building out-of-tree:
=====================
Buildroot supports building out of tree with a syntax similar
to the Linux kernel. To use it, add O=<directory> to the
make command line, E.G.:
$ make O=/tmp/build
And all the output files (including .config) will be located under /tmp/build.
More finegrained configuration:
===============================
You can specify a config-file for uClibc:
$ make UCLIBC_CONFIG_FILE=/my/uClibc.config
And you can specify a config-file for busybox:
$ make BUSYBOX_CONFIG_FILE=/my/busybox.config
To use a non-standard host-compiler (if you do not have 'gcc'),
make sure that the compiler is in your PATH and that the library paths are
setup properly, if your compiler is built dynamically:
$ make HOSTCC=gcc-4.3.orig HOSTCXX=gcc-4.3-mine
Depending on your configuration, there are some targets you can use to
use menuconfig of certain packages. This includes:
$ make HOSTCC=gcc-4.3 linux-menuconfig
$ make HOSTCC=gcc-4.3 uclibc-menuconfig
$ make HOSTCC=gcc-4.3 busybox-menuconfig
Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org