ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-19 12:57:53 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
ff75c69df0
crosstool-ng/config/kernel.in

37 lines
956 B
Plaintext
Raw Normal View History

Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
# Kernel options
Generate the kernel config choice, rather than having it hard-coded: - change the menu label from 'Target OS' to 'Operating System', - bare-metal is a kind of kernel (OS), rename to 'bare-metal' from 'none', - update the kconfig.mk to generate the kernel choice entries, - update glibc&eglibc kernel version option accordingly. Update the debug & tools confiog file generation to match with arch & kernel. Print terse command lines when building in kconfig/ (a-la Linux kernel). Fix the makefile rules in kconfig/kconfig.mk to be /simple/ rules. /trunk/kconfig/kconfig.mk | 117 81 36 0 +++++++++++++++++++++---------- /trunk/config/kernel/linux.in | 4 4 0 0 + /trunk/config/kernel/bare-metal.experimental.in | 15 15 0 0 ++++ /trunk/config/kernel.in | 33 5 28 0 +-------- /trunk/config/libc/glibc-eglibc-common.in | 4 2 2 0 5 files changed, 107 insertions(+), 66 deletions(-)
2008-09-16 17:39:40 +00:00
menu "Operating System"
Move around the BARE_METAL config entry outside of the bare metal /kernel/ entry: there might be different setups that causes a bare metal compiler. /trunk/config/kernel/bare-metal.experimental.in | 12 4 8 0 ++++-------- /trunk/config/kernel.in | 6 6 0 0 ++++++ 2 files changed, 10 insertions(+), 8 deletions(-)
2008-09-28 21:31:13 +00:00
# Config option used throughout the config and code to determine wether
Merge the /deve/uclinux branch back to /trunk: - add support for uClinux, the MMU-less ports of Linux. -------- diffstat follows -------- /trunk/scripts/build/kernel/linux.sh | 100 1 99 0 --------------- /trunk/steps.mk | 1 1 0 0 + /trunk/config/kernel/linux.in | 247 0 247 0 ------------------------------------- /trunk/config/kernel.in | 2 1 1 0 /trunk/config/libc/glibc.in | 2 1 1 0 /trunk/config/libc/eglibc.in | 2 1 1 0 /trunk/config/libc/glibc-eglibc.in-common | 5 5 0 0 + /trunk/config/config.in | 1 1 0 0 + 8 files changed, 11 insertions(+), 349 deletions(-)
2009-05-13 20:55:15 +00:00
# we have a kernel or not (there might be different bare metal stuff)...
Convert the rest of packages to new framework Signed-off-by: Alexey Neyman <stilor@att.net>
2017-05-27 07:01:49 +00:00
# FIXME use CT_KERNEL_bare_metal instead
Move around the BARE_METAL config entry outside of the bare metal /kernel/ entry: there might be different setups that causes a bare metal compiler. /trunk/config/kernel/bare-metal.experimental.in | 12 4 8 0 ++++-------- /trunk/config/kernel.in | 6 6 0 0 ++++++ 2 files changed, 10 insertions(+), 8 deletions(-)
2008-09-28 21:31:13 +00:00
config BARE_METAL
bool
Convert the rest of packages to new framework Signed-off-by: Alexey Neyman <stilor@att.net>
2017-05-27 07:01:49 +00:00
# FIXME use CT_KERNEL_windows instead
libc/mingw: replace mingw32 with generic mingw Replace the 32-bit-only mingw32 with mingw-w64 that is capable of building toolchains for both 32-bit and 64-bit Windows. kernel/mingw: replace mingw32 with generic Windows kernel/windows: New windows kernel supporting 32 and 64 bit arch libc/mingw: Remove old options patches: Remove old mingw libc options' patches Signed-off-by: "Yann Diorcet" <diorcet.yann@gmail.com> [yann.morin.1998@free.fr: array var in libc/mingw.sh, typos] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Message-Id: <b045ac08fc9eac2e5ee3.1352898499@blackmint> Patchwork-Id: 198901
2012-11-14 13:05:49 +00:00
config WINDOWS
kernel: add mingw 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>
2010-07-11 19:36:20 +00:00
bool
config: introduce the KERNEL_SUPPORTS_SHARED_LIBS silent config option The target OSes will be able to select this option if they support shared libraries, instead of having "Build shared libaries" depend on each OS.
2009-08-30 14:44:59 +00:00
# Each target OS (aka kernel) that support shared libraries can select
# this, so the user can decide whether or not to build a shared library
# enabled toolchain
config KERNEL_SUPPORTS_SHARED_LIBS
bool
Get rid of config.gen Instead, prepare the files as a part of bootstrap and install them. This avoids rebuilding these files in each working directory; they don't change anyway as they are generated from the same installed source. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 01:41:50 +00:00
source "config/gen/kernel.in"
Make bare-metal a kernel selection. /trunk/config/kernel.in | 22 14 8 0 ++++++++++++++-------- /trunk/config/target.in | 13 0 13 0 ------------- 2 files changed, 14 insertions(+), 21 deletions(-)
2008-09-15 09:43:35 +00:00
config: move the "build shared libraries" option to the OS menu The "Build shared libraries" config option is dependant on the type of "Target OS". Moving this options to the "Target OS" sub-menu is also better in the user perspective: he/she no longer needs to go back and forth to see if he/she missed any option.
2009-08-30 14:54:30 +00:00
comment "Common kernel options"
config SHARED_LIBS
bool
prompt "Build shared libraries"
depends on KERNEL_SUPPORTS_SHARED_LIBS
default y
help
Say 'y' here, unless you don't want shared libraries.
You might not want shared libraries if you're building for a target that
don't support it (maybe some nommu targets, for example, or bare metal).
Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
endmenu
Reference in New Issue Copy Permalink