2007-02-06 19:19:38 +01:00
|
|
|
#
|
|
|
|
|
|
2007-09-26 23:12:38 +02:00
|
|
|
if BR2_TOOLCHAIN_EXTERNAL
|
|
|
|
|
comment "External Toolchain Options"
|
|
|
|
|
|
2007-02-06 19:19:38 +01:00
|
|
|
|
|
|
|
|
config BR2_TOOLCHAIN_EXTERNAL_LIB_C
|
|
|
|
|
string "The core C library from the external toolchain"
|
2008-06-16 14:22:45 +02:00
|
|
|
default "libc.so.0"
|
2007-02-06 19:19:38 +01:00
|
|
|
help
|
|
|
|
|
Specify the core C shared library found in the external
|
|
|
|
|
toolchain. This is required in addition to any other
|
|
|
|
|
libraries to be copied.
|
|
|
|
|
|
|
|
|
|
config BR2_TOOLCHAIN_EXTERNAL_LIBS
|
|
|
|
|
string "Libraries to copy from the external toolchain"
|
2008-06-16 14:22:45 +02:00
|
|
|
default "ld-uClibc.so.0 libcrypt.so.0 libdl.so.0 libgcc_s.so libm.so.0 libnsl.so.0 libpthread.so.0 libresolv.so.0 librt.so.0 libutil.so.0"
|
2007-02-06 19:19:38 +01:00
|
|
|
help
|
|
|
|
|
A space separated list of the shared libraries to be copied
|
|
|
|
|
from the external toolchain into the root filesystem. Only
|
|
|
|
|
the top-level name is needed, i.e. libc.so, libpthread.so as
|
|
|
|
|
the actual shared library symlinked to will be copied also.
|
|
|
|
|
|
|
|
|
|
config BR2_TOOLCHAIN_EXTERNAL_STRIP
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
prompt "Strip shared libraries"
|
|
|
|
|
help
|
|
|
|
|
Strip shared libraries copied from the external toolchain.
|
|
|
|
|
|
|
|
|
|
comment "Common Toolchain Options"
|
|
|
|
|
|
2007-04-28 19:10:31 +02:00
|
|
|
source "toolchain/gdb/Config.in.2"
|
|
|
|
|
|
2007-02-06 19:19:38 +01:00
|
|
|
config BR2_TOOLCHAIN_EXTERNAL_PATH
|
|
|
|
|
string "External toolchain path"
|
2008-06-16 14:22:45 +02:00
|
|
|
default "/path/to/staging_dir/usr"
|
2007-02-06 19:19:38 +01:00
|
|
|
help
|
|
|
|
|
Path to where the external toolchain is installed.
|
|
|
|
|
|
|
|
|
|
config BR2_TOOLCHAIN_EXTERNAL_PREFIX
|
|
|
|
|
string "External toolchain prefix"
|
2008-06-16 14:22:45 +02:00
|
|
|
default "$(ARCH)-linux"
|
2007-02-06 19:19:38 +01:00
|
|
|
help
|
|
|
|
|
This the the external toolchain prefix. For example:
|
|
|
|
|
armeb-unknown-linux-gnu, mipsel-unknown-linux-gnu, etc.
|
|
|
|
|
|
2007-04-28 19:10:31 +02:00
|
|
|
choice
|
|
|
|
|
prompt "Thread library implementation"
|
|
|
|
|
default BR2_EXT_PTHREADS_OLD
|
|
|
|
|
help
|
|
|
|
|
Select the version of libpthreads used in the external toolchain.
|
|
|
|
|
|
|
|
|
|
config BR2_EXT_PTHREADS_NONE
|
|
|
|
|
bool
|
|
|
|
|
prompt "none"
|
|
|
|
|
|
|
|
|
|
config BR2_EXT_PTHREADS
|
|
|
|
|
bool
|
|
|
|
|
prompt "linuxthreads"
|
|
|
|
|
|
|
|
|
|
config BR2_EXT_PTHREADS_OLD
|
|
|
|
|
bool
|
|
|
|
|
prompt "linuxthreads (stable/old)"
|
|
|
|
|
|
|
|
|
|
config BR2_EXT_PTHREADS_NATIVE
|
|
|
|
|
bool
|
|
|
|
|
prompt "Native POSIX Threading (NPTL)"
|
|
|
|
|
endchoice
|
|
|
|
|
|
2007-02-06 19:19:38 +01:00
|
|
|
config BR2_LARGEFILE
|
External toolchain support improvements
Improve external toolchain support
* Do not put kernel-headers in the dependencies of BASE_TARGETS in
the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
are already supposed to be part of the external toolchain, so
there's no need to download, extract and install them.
* In the configuration system, don't display the kernel headers
version selection list when an external toolchain is selected. This
is implemented by moving the source
"toolchain/kernel-headers/Config.in" inside the if
BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
* Change the description and help message of the BR2_LARGEFILE,
BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
toolchain/external-toolchain/Config.in. In the case of an external
toolchain, the semantic of these options is not to enable large
file support, IPV6 or RPC (since the toolchain is already compiled,
it has been decided previously). Their semantic is to let Buildroot
know about the characteristics of the external toolchain being
used.
As an improvement, we could guess these values automatically:
- for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
bits/uClibc_config.h in the libc headers directory.
- for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the
same file
- for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in
the same file
- for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep
-- "--with-float=soft"
But I'm not sure how this would be possible, since these values are
used at configuration-time by other configuration options, not only
at build time.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-03 11:18:39 +01:00
|
|
|
bool "Toolchain supports large files (> 2 GB) ?"
|
2007-02-06 19:19:38 +01:00
|
|
|
depends on !BR2_cris
|
|
|
|
|
default y
|
|
|
|
|
help
|
External toolchain support improvements
Improve external toolchain support
* Do not put kernel-headers in the dependencies of BASE_TARGETS in
the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
are already supposed to be part of the external toolchain, so
there's no need to download, extract and install them.
* In the configuration system, don't display the kernel headers
version selection list when an external toolchain is selected. This
is implemented by moving the source
"toolchain/kernel-headers/Config.in" inside the if
BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
* Change the description and help message of the BR2_LARGEFILE,
BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
toolchain/external-toolchain/Config.in. In the case of an external
toolchain, the semantic of these options is not to enable large
file support, IPV6 or RPC (since the toolchain is already compiled,
it has been decided previously). Their semantic is to let Buildroot
know about the characteristics of the external toolchain being
used.
As an improvement, we could guess these values automatically:
- for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
bits/uClibc_config.h in the libc headers directory.
- for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the
same file
- for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in
the same file
- for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep
-- "--with-float=soft"
But I'm not sure how this would be possible, since these values are
used at configuration-time by other configuration options, not only
at build time.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-03 11:18:39 +01:00
|
|
|
Set this option if the external toolchain supports large
|
|
|
|
|
files (> 2 GB)
|
|
|
|
|
|
2007-02-06 19:19:38 +01:00
|
|
|
|
2007-07-17 02:18:54 +02:00
|
|
|
config BR2_INET_IPV6
|
External toolchain support improvements
Improve external toolchain support
* Do not put kernel-headers in the dependencies of BASE_TARGETS in
the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
are already supposed to be part of the external toolchain, so
there's no need to download, extract and install them.
* In the configuration system, don't display the kernel headers
version selection list when an external toolchain is selected. This
is implemented by moving the source
"toolchain/kernel-headers/Config.in" inside the if
BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
* Change the description and help message of the BR2_LARGEFILE,
BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
toolchain/external-toolchain/Config.in. In the case of an external
toolchain, the semantic of these options is not to enable large
file support, IPV6 or RPC (since the toolchain is already compiled,
it has been decided previously). Their semantic is to let Buildroot
know about the characteristics of the external toolchain being
used.
As an improvement, we could guess these values automatically:
- for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
bits/uClibc_config.h in the libc headers directory.
- for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the
same file
- for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in
the same file
- for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep
-- "--with-float=soft"
But I'm not sure how this would be possible, since these values are
used at configuration-time by other configuration options, not only
at build time.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-03 11:18:39 +01:00
|
|
|
bool "Toolchain supports IPv6 ?"
|
2007-07-17 02:18:54 +02:00
|
|
|
help
|
External toolchain support improvements
Improve external toolchain support
* Do not put kernel-headers in the dependencies of BASE_TARGETS in
the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
are already supposed to be part of the external toolchain, so
there's no need to download, extract and install them.
* In the configuration system, don't display the kernel headers
version selection list when an external toolchain is selected. This
is implemented by moving the source
"toolchain/kernel-headers/Config.in" inside the if
BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
* Change the description and help message of the BR2_LARGEFILE,
BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
toolchain/external-toolchain/Config.in. In the case of an external
toolchain, the semantic of these options is not to enable large
file support, IPV6 or RPC (since the toolchain is already compiled,
it has been decided previously). Their semantic is to let Buildroot
know about the characteristics of the external toolchain being
used.
As an improvement, we could guess these values automatically:
- for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
bits/uClibc_config.h in the libc headers directory.
- for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the
same file
- for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in
the same file
- for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep
-- "--with-float=soft"
But I'm not sure how this would be possible, since these values are
used at configuration-time by other configuration options, not only
at build time.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-03 11:18:39 +01:00
|
|
|
Set this option if the external toolchain supports IPv6.
|
2007-07-17 02:18:54 +02:00
|
|
|
|
|
|
|
|
config BR2_INET_RPC
|
External toolchain support improvements
Improve external toolchain support
* Do not put kernel-headers in the dependencies of BASE_TARGETS in
the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
are already supposed to be part of the external toolchain, so
there's no need to download, extract and install them.
* In the configuration system, don't display the kernel headers
version selection list when an external toolchain is selected. This
is implemented by moving the source
"toolchain/kernel-headers/Config.in" inside the if
BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
* Change the description and help message of the BR2_LARGEFILE,
BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
toolchain/external-toolchain/Config.in. In the case of an external
toolchain, the semantic of these options is not to enable large
file support, IPV6 or RPC (since the toolchain is already compiled,
it has been decided previously). Their semantic is to let Buildroot
know about the characteristics of the external toolchain being
used.
As an improvement, we could guess these values automatically:
- for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
bits/uClibc_config.h in the libc headers directory.
- for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the
same file
- for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in
the same file
- for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep
-- "--with-float=soft"
But I'm not sure how this would be possible, since these values are
used at configuration-time by other configuration options, not only
at build time.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-03 11:18:39 +01:00
|
|
|
bool "Toolchain supports RPC ?"
|
2007-07-17 02:18:54 +02:00
|
|
|
help
|
External toolchain support improvements
Improve external toolchain support
* Do not put kernel-headers in the dependencies of BASE_TARGETS in
the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
are already supposed to be part of the external toolchain, so
there's no need to download, extract and install them.
* In the configuration system, don't display the kernel headers
version selection list when an external toolchain is selected. This
is implemented by moving the source
"toolchain/kernel-headers/Config.in" inside the if
BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
* Change the description and help message of the BR2_LARGEFILE,
BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
toolchain/external-toolchain/Config.in. In the case of an external
toolchain, the semantic of these options is not to enable large
file support, IPV6 or RPC (since the toolchain is already compiled,
it has been decided previously). Their semantic is to let Buildroot
know about the characteristics of the external toolchain being
used.
As an improvement, we could guess these values automatically:
- for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
bits/uClibc_config.h in the libc headers directory.
- for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the
same file
- for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in
the same file
- for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep
-- "--with-float=soft"
But I'm not sure how this would be possible, since these values are
used at configuration-time by other configuration options, not only
at build time.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-03 11:18:39 +01:00
|
|
|
Set this option if the external toolchain supports RPC.
|
2007-07-17 02:18:54 +02:00
|
|
|
|
2007-02-06 19:19:38 +01:00
|
|
|
config BR2_SOFT_FLOAT
|
External toolchain support improvements
Improve external toolchain support
* Do not put kernel-headers in the dependencies of BASE_TARGETS in
the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
are already supposed to be part of the external toolchain, so
there's no need to download, extract and install them.
* In the configuration system, don't display the kernel headers
version selection list when an external toolchain is selected. This
is implemented by moving the source
"toolchain/kernel-headers/Config.in" inside the if
BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
* Change the description and help message of the BR2_LARGEFILE,
BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
toolchain/external-toolchain/Config.in. In the case of an external
toolchain, the semantic of these options is not to enable large
file support, IPV6 or RPC (since the toolchain is already compiled,
it has been decided previously). Their semantic is to let Buildroot
know about the characteristics of the external toolchain being
used.
As an improvement, we could guess these values automatically:
- for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
bits/uClibc_config.h in the libc headers directory.
- for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the
same file
- for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in
the same file
- for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep
-- "--with-float=soft"
But I'm not sure how this would be possible, since these values are
used at configuration-time by other configuration options, not only
at build time.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-03 11:18:39 +01:00
|
|
|
bool "Toolchain supports soft float ?"
|
2007-02-06 19:19:38 +01:00
|
|
|
depends on BR2_arm || BR2_armeb || BR2_mips || BR2_mipsel || BR2_powerpc
|
|
|
|
|
help
|
External toolchain support improvements
Improve external toolchain support
* Do not put kernel-headers in the dependencies of BASE_TARGETS in
the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers
are already supposed to be part of the external toolchain, so
there's no need to download, extract and install them.
* In the configuration system, don't display the kernel headers
version selection list when an external toolchain is selected. This
is implemented by moving the source
"toolchain/kernel-headers/Config.in" inside the if
BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2.
* Change the description and help message of the BR2_LARGEFILE,
BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in
toolchain/external-toolchain/Config.in. In the case of an external
toolchain, the semantic of these options is not to enable large
file support, IPV6 or RPC (since the toolchain is already compiled,
it has been decided previously). Their semantic is to let Buildroot
know about the characteristics of the external toolchain being
used.
As an improvement, we could guess these values automatically:
- for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in
bits/uClibc_config.h in the libc headers directory.
- for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the
same file
- for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in
the same file
- for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep
-- "--with-float=soft"
But I'm not sure how this would be possible, since these values are
used at configuration-time by other configuration options, not only
at build time.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-11-03 11:18:39 +01:00
|
|
|
Set this option if the external toolchain supports soft float.
|
2007-02-06 19:19:38 +01:00
|
|
|
|
2008-11-03 11:37:27 +01:00
|
|
|
config BR2_GCC_CROSS_CXX
|
|
|
|
|
bool "Toolchain has C++ cross-compiler ?"
|
|
|
|
|
help
|
|
|
|
|
Set this option if the external toolchain has a C++
|
|
|
|
|
cross-compiler.
|
|
|
|
|
|
2007-02-06 19:19:38 +01:00
|
|
|
config BR2_TARGET_OPTIMIZATION
|
|
|
|
|
string "Target Optimizations"
|
|
|
|
|
default "-Os -pipe"
|
|
|
|
|
help
|
|
|
|
|
Optimizations to use when building for the target host.
|
|
|
|
|
|
2007-09-26 23:12:38 +02:00
|
|
|
endif
|
