mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2024-12-24 23:16:42 +00:00
b81d232a9b
Add the option to build a cross-compiler for kernel type 'mingw'. The resulting cross-compiler can be used to build applications on a Linux host that can be run on a Windows target. Compiler is build using the mingwrt and w32-api packages aviable from the MinGW project (http://sourceforge.net/projects/mingw). The windows headers (w32-api package) are extracting with the kernel_headers step The libraries and other headers from both packages are build and installed in the various steps of libc Signed-off-by: Bart vdr Meulen <bartvdrmeulen@gmail.com> [yann.morin.1998@anciens.enib.fr: fix kernel headers comment, don't "return 0"] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
116 lines
2.7 KiB
Plaintext
116 lines
2.7 KiB
Plaintext
# glibc options
|
|
# depends on ! MINGW32 && ! BARE_METAL && ARCH_USE_MMU
|
|
|
|
config LIBC_glibc
|
|
select LIBC_SUPPORT_NPTL
|
|
select LIBC_SUPPORT_LINUXTHREADS
|
|
help
|
|
The de-facto standard for Linux distributions.
|
|
Feature-rich, but large... Most usefull for desktop-like systems.
|
|
|
|
choice
|
|
bool
|
|
prompt "Retrieval method"
|
|
default LIBC_GLIBC_TARBALL
|
|
|
|
config LIBC_GLIBC_TARBALL
|
|
bool
|
|
prompt "Released tarball"
|
|
help
|
|
Until end of Februrary 2009, there was no tarball for glibc releases
|
|
2.8 and later. This was intentional.
|
|
|
|
Then, all of a sudden, tarballs for those releases have appeared at the
|
|
traditional download place (ftp.gnu.org).
|
|
|
|
Some of the glibc people argue that fixes are committed to the maintenance
|
|
branch, and thus it is the best plac e to retrieve the glibc from.
|
|
On the other hand, it might be preferable to always generate a toolchain
|
|
using a known code-base, so the toolchain can be reproducible.
|
|
|
|
For version prior to 2.8, tarballs were readily available.
|
|
|
|
If you want your toolchain to really be reproducible, say 'Y' here.
|
|
If you can live with a moving code-base, look at the other choice
|
|
entries, below.
|
|
|
|
endchoice
|
|
|
|
choice
|
|
bool
|
|
prompt "glibc version"
|
|
# Don't remove next line
|
|
# CT_INSERT_VERSION_BELOW
|
|
|
|
config LIBC_GLIBC_V_2_11_1
|
|
bool
|
|
prompt "2.11.1 (EXPERIMENTAL)"
|
|
depends on EXPERIMENTAL
|
|
|
|
config LIBC_GLIBC_V_2_11
|
|
bool
|
|
prompt "2.11 (EXPERIMENTAL)"
|
|
depends on EXPERIMENTAL
|
|
|
|
config LIBC_V_2_10_1
|
|
bool
|
|
prompt "2.10.1 (EXPERIMENTAL)"
|
|
depends on EXPERIMENTAL
|
|
select LIBC_GLIBC_USE_PORTS
|
|
|
|
config LIBC_V_2_9
|
|
bool
|
|
prompt "2.9"
|
|
|
|
config LIBC_V_2_8
|
|
bool
|
|
prompt "2.8"
|
|
|
|
config LIBC_V_2_7
|
|
bool
|
|
prompt "2.7 (OBSOLETE)"
|
|
depends on OBSOLETE
|
|
|
|
config LIBC_V_2_6_1
|
|
bool
|
|
prompt "2.6.1 (OBSOLETE)"
|
|
depends on OBSOLETE
|
|
|
|
config LIBC_V_2_6
|
|
bool
|
|
prompt "2.6 (OBSOLETE)"
|
|
depends on OBSOLETE
|
|
|
|
config LIBC_V_2_5_1
|
|
bool
|
|
prompt "2.5.1 (OBSOLETE)"
|
|
depends on OBSOLETE
|
|
|
|
config LIBC_V_2_5
|
|
bool
|
|
prompt "2.5 (OBSOLETE)"
|
|
depends on OBSOLETE
|
|
|
|
config LIBC_V_2_3_6
|
|
bool
|
|
prompt "2.3.6 (OBSOLETE)"
|
|
depends on OBSOLETE
|
|
|
|
endchoice
|
|
|
|
config LIBC_VERSION
|
|
string
|
|
# Don't remove next line
|
|
# CT_INSERT_VERSION_STRING_BELOW
|
|
default "2.11.1" if LIBC_GLIBC_V_2_11_1
|
|
default "2.11" if LIBC_GLIBC_V_2_11
|
|
default "2.10.1" if LIBC_V_2_10_1
|
|
default "2.9" if LIBC_V_2_9
|
|
default "2.8" if LIBC_V_2_8
|
|
default "2.7" if LIBC_V_2_7
|
|
default "2.6.1" if LIBC_V_2_6_1
|
|
default "2.6" if LIBC_V_2_6
|
|
default "2.5.1" if LIBC_V_2_5_1
|
|
default "2.5" if LIBC_V_2_5
|
|
default "2.3.6" if LIBC_V_2_3_6
|