jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-27 21:26:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs/manual: update to mention eglibc support in Buildroot toolchain backend

Browse Source 
[Peter: minor tweak]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
This commit is contained in:
Thomas Petazzoni 2013-06-30 21:29:13 +02:00 committed by Peter Korsgaard
parent 8d29893893
commit 30224b8ee2
1 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
docs/manual/configure.txt
View File

@ -72,11 +72,12 @@ The _internal toolchain backend_ is the backend where Buildroot builds
by itself a cross-compilation toolchain, before building the userspace by itself a cross-compilation toolchain, before building the userspace
applications and libraries for your target embedded system. applications and libraries for your target embedded system.
This backend is the historical backend of Buildroot, and is limited to This backend is the historical backend of Buildroot, and has been
the usage of the http://www.uclibc.org[uClibc C library] (i.e, the limited for a long time to the usage of the
_glibc_ and _eglibc_ C libraries are not supported by this backend, http://www.uclibc.org[uClibc C library]. Support for the _eglibc_ C
see the _External toolchain backend_ and _Crosstool-NG toolchain library has been added in 2013 and is at this point considered
backend_ for solutions to use either _glibc_ or _eglibc_). experimental. See the _External toolchain backend_ and _Crosstool-NG
toolchain backend_ for other solutions to use _glibc_ or _eglibc_.
Once you have selected this backend, a number of options appear. The Once you have selected this backend, a number of options appear. The
most important ones allow to: most important ones allow to:
@ -99,29 +100,29 @@ most important ones allow to:
the C library might be using interfaces that are not provided by the C library might be using interfaces that are not provided by
your Linux kernel. your Linux kernel.
* Change the version and the configuration of the uClibc C * Change the version and the configuration of the uClibc C library
library. The default options are usually fine. However, if you (if uClibc is selected). The default options are usually
really need to specifically customize the configuration of your fine. However, if you really need to specifically customize the
uClibc C library, you can pass a specific configuration file configuration of your uClibc C library, you can pass a specific
here. Or alternatively, you can run the +make uclibc-menuconfig+ configuration file here. Or alternatively, you can run the +make
command to get access to uClibc's configuration interface. Note uclibc-menuconfig+ command to get access to uClibc's configuration
that all packages in Buildroot are tested against the default interface. Note that all packages in Buildroot are tested against
uClibc configuration bundled in Buildroot: if you deviate from this the default uClibc configuration bundled in Buildroot: if you
configuration by removing features from uClibc, some packages may deviate from this configuration by removing features from uClibc,
no longer build. some packages may no longer build.
* Change the version of the GCC compiler and binutils. * Change the version of the GCC compiler and binutils.
* Select a number of toolchain options: whether the toolchain should * Select a number of toolchain options (uClibc only): whether the
have largefile support (i.e support for files larger than 2 GB on toolchain should have largefile support (i.e support for files
32 bits systems), IPv6 support, RPC support (used mainly for NFS), larger than 2 GB on 32 bits systems), IPv6 support, RPC support
wide-char support, locale support (for internationalization), C++ (used mainly for NFS), wide-char support, locale support (for
support, thread support. Depending on which options you choose, the internationalization), C++ support, thread support. Depending on
number of userspace applications and libraries visible in Buildroot which options you choose, the number of userspace applications and
menus will change: many applications and libraries require certain libraries visible in Buildroot menus will change: many applications
toolchain options to be enabled. Most packages show a comment when and libraries require certain toolchain options to be enabled. Most
a certain toolchain option is required to be able to enable those packages show a comment when a certain toolchain option is required
packages. to be able to enable those packages.
It is worth noting that whenever one of those options is modified, It is worth noting that whenever one of those options is modified,
then the entire toolchain and system must be rebuilt. See then the entire toolchain and system must be rebuilt. See
@ -137,7 +138,6 @@ Drawbacks of this backend:
* Rebuilding the toolchain is needed when doing +make clean+, which * Rebuilding the toolchain is needed when doing +make clean+, which
takes time. If you're trying to reduce your build time, consider takes time. If you're trying to reduce your build time, consider
using the _External toolchain backend_. using the _External toolchain backend_.
* Limited to the _uClibc_ C library.
[[external-toolchain-backend]] [[external-toolchain-backend]]
External toolchain backend External toolchain backend