From dd862bd7a46c6bb3f1a9d4bda7bf12c81dd7004b Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN\"" Date: Thu, 17 Apr 2008 20:26:25 +0000 Subject: Move config files around, and clean up the mess in the config/ directory. config/kernel/kernel_linux.in | 12 6 6 0 +- config/paths.in | 89 0 89 0 ---------------- config/kernel_linux_headers_install.in | 168 0 168 0 ------------------------------ config/kernel.in | 2 1 1 0 config/kernel_linux_headers_copy.in | 42 0 42 0 -------- config/cc.in | 2 1 1 0 config/logging.in | 110 0 110 0 -------------------- config/build-behave.in | 45 0 45 0 -------- config/libc_uClibc.in | 101 0 101 0 ------------------ config/kernel_linux_headers_sanitised.in | 62 0 62 0 ----------- config/ct-behave.in | 82 0 82 0 --------------- config/kernel_linux.in | 134 0 134 0 ------------------------ config/global.in | 10 5 5 0 +- config/download_extract.in | 171 0 171 0 ------------------------------- config/cc_gcc.in | 130 0 130 0 ------------------------ config/libc_glibc.in | 124 0 124 0 ---------------------- config/libc.in | 4 2 2 0 17 files changed, 15 insertions(+), 1273 deletions(-) diff --git a/config/build-behave.in b/config/build-behave.in deleted file mode 100644 index 7c1175c..0000000 --- a/config/build-behave.in +++ /dev/null @@ -1,45 +0,0 @@ -# Options related to how the build behaves - -comment "Build behavior" - -config PARALLEL_JOBS - int - prompt "Number of parallel jobs" - default 1 - help - Number of jobs make will be allowed to run concurently. - Set this higher than the number of processors you have, but not too high. - A good rule of thumb is twice the number of processors you have. - - Enter 1 (or 0) to have only one job at a time. - -config LOAD - int - prompt "Maximum allowed load" - default 0 - help - Specifies that no new jobs should be started if there are others jobs - running and the load average is at least this value. - - Makes sense on SMP machines only. - - Enter 0 to have no limit on the load average. - - Note: only the integer part of the load is allowed here (you can't enter - 0.75 for example). - -config NICE - int - prompt "Nice level" - default 0 - range 0 19 - help - Renices the build process up. - -config USE_PIPES - bool - prompt "Use -pipe" - default y - help - Use gcc's option -pipe to use pipes rather than temp files when building - the toolchain. diff --git a/config/cc.in b/config/cc.in index cdd4581..2b74fba 100644 --- a/config/cc.in +++ b/config/cc.in @@ -32,7 +32,7 @@ config CC default "gcc" if CC_GCC if CC_GCC -source config/cc_gcc.in +source config/cc/cc_gcc.in endif config CC_SUPPORT_CXX diff --git a/config/cc/cc_gcc.in b/config/cc/cc_gcc.in new file mode 100644 index 0000000..9df1dfc --- /dev/null +++ b/config/cc/cc_gcc.in @@ -0,0 +1,130 @@ +# Compiler options + +choice + bool + prompt "gcc version" + +config CC_V_2_95_3 + bool + prompt "2.95.3 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_3_2_3 + bool + prompt "3.2.3 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_3_3_6 + bool + prompt "3.3.6 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_3_4_6 + bool + prompt "3.4.6 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_4_0_0 + bool + prompt "4.0.0 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_4_0_1 + bool + prompt "4.0.1 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_4_0_2 + bool + prompt "4.0.2 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_4_0_3 + bool + prompt "4.0.3 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_4_0_4 + bool + prompt "4.0.4" + +config CC_V_4_1_0 + bool + prompt "4.1.0 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_4_1_1 + bool + prompt "4.1.1 (OBSOLETE)" + depends on OBSOLETE + +config CC_V_4_1_2 + bool + prompt "4.1.2" + +config CC_V_4_2_0 + bool + prompt "4.2.0" + +config CC_V_4_2_1 + bool + prompt "4.2.1" + +config CC_V_4_2_2 + bool + prompt "4.2.2" + +config CC_V_4_2_3 + bool + prompt "4.2.3 (EXPERIMENTAL)" + depends on EXPERIMENTAL + +# CT_INSERT_VERSION_ABOVE +# Don't remove above line! +endchoice + +config CC_VERSION + string + default "2.95.3" if CC_V_2_95_3 + default "3.2.3" if CC_V_3_2_3 + default "3.3.6" if CC_V_3_3_6 + default "3.4.6" if CC_V_3_4_6 + default "4.0.0" if CC_V_4_0_0 + default "4.0.1" if CC_V_4_0_1 + default "4.0.2" if CC_V_4_0_2 + default "4.0.3" if CC_V_4_0_3 + default "4.0.4" if CC_V_4_0_4 + default "4.1.0" if CC_V_4_1_0 + default "4.1.1" if CC_V_4_1_1 + default "4.1.2" if CC_V_4_1_2 + default "4.2.0" if CC_V_4_2_0 + default "4.2.1" if CC_V_4_2_1 + default "4.2.2" if CC_V_4_2_2 + default "4.2.3" if CC_V_4_2_3 +# CT_INSERT_VERSION_STRING_ABOVE +# Don't remove above line! + +config CC_CXA_ATEXIT + bool + prompt "__cxa_atexit" + default "y" + help + If you get the missing symbol "__cxa_atexit" when building C++ programs, + you might want to try disabling this option. + +config CC_CORE_EXTRA_CONFIG + string + prompt "Core gcc extra config" + default "" + help + Extra flags to pass onto ./configure when configuring the core gcc. + + The core gcc is a stripped down, C-only compiler needed to build + the C library. Kinda bootstrap gcc, if you wish. + +config CC_EXTRA_CONFIG + string + prompt "gcc extra config" + default "" + help + Extra flags to pass onto ./configure when configuring gcc. diff --git a/config/cc_gcc.in b/config/cc_gcc.in deleted file mode 100644 index 9df1dfc..0000000 --- a/config/cc_gcc.in +++ /dev/null @@ -1,130 +0,0 @@ -# Compiler options - -choice - bool - prompt "gcc version" - -config CC_V_2_95_3 - bool - prompt "2.95.3 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_3_2_3 - bool - prompt "3.2.3 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_3_3_6 - bool - prompt "3.3.6 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_3_4_6 - bool - prompt "3.4.6 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_4_0_0 - bool - prompt "4.0.0 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_4_0_1 - bool - prompt "4.0.1 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_4_0_2 - bool - prompt "4.0.2 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_4_0_3 - bool - prompt "4.0.3 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_4_0_4 - bool - prompt "4.0.4" - -config CC_V_4_1_0 - bool - prompt "4.1.0 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_4_1_1 - bool - prompt "4.1.1 (OBSOLETE)" - depends on OBSOLETE - -config CC_V_4_1_2 - bool - prompt "4.1.2" - -config CC_V_4_2_0 - bool - prompt "4.2.0" - -config CC_V_4_2_1 - bool - prompt "4.2.1" - -config CC_V_4_2_2 - bool - prompt "4.2.2" - -config CC_V_4_2_3 - bool - prompt "4.2.3 (EXPERIMENTAL)" - depends on EXPERIMENTAL - -# CT_INSERT_VERSION_ABOVE -# Don't remove above line! -endchoice - -config CC_VERSION - string - default "2.95.3" if CC_V_2_95_3 - default "3.2.3" if CC_V_3_2_3 - default "3.3.6" if CC_V_3_3_6 - default "3.4.6" if CC_V_3_4_6 - default "4.0.0" if CC_V_4_0_0 - default "4.0.1" if CC_V_4_0_1 - default "4.0.2" if CC_V_4_0_2 - default "4.0.3" if CC_V_4_0_3 - default "4.0.4" if CC_V_4_0_4 - default "4.1.0" if CC_V_4_1_0 - default "4.1.1" if CC_V_4_1_1 - default "4.1.2" if CC_V_4_1_2 - default "4.2.0" if CC_V_4_2_0 - default "4.2.1" if CC_V_4_2_1 - default "4.2.2" if CC_V_4_2_2 - default "4.2.3" if CC_V_4_2_3 -# CT_INSERT_VERSION_STRING_ABOVE -# Don't remove above line! - -config CC_CXA_ATEXIT - bool - prompt "__cxa_atexit" - default "y" - help - If you get the missing symbol "__cxa_atexit" when building C++ programs, - you might want to try disabling this option. - -config CC_CORE_EXTRA_CONFIG - string - prompt "Core gcc extra config" - default "" - help - Extra flags to pass onto ./configure when configuring the core gcc. - - The core gcc is a stripped down, C-only compiler needed to build - the C library. Kinda bootstrap gcc, if you wish. - -config CC_EXTRA_CONFIG - string - prompt "gcc extra config" - default "" - help - Extra flags to pass onto ./configure when configuring gcc. diff --git a/config/ct-behave.in b/config/ct-behave.in deleted file mode 100644 index 737028b..0000000 --- a/config/ct-behave.in +++ /dev/null @@ -1,82 +0,0 @@ -# Options specific to crosstool-NG overall behavior - -comment "crosstool-NG behavior" - -config OBSOLETE - bool - prompt "Use obsolete features" - default n - help - If you set this to Y, you will be able to select obsolete features. - - Such obsolete features are the use of old kernel headers, old - gcc versions, etc... - -config EXPERIMENTAL - bool - prompt "Try features marked as EXPERIMENTAL" - default n - help - If you set this to Y, then you will be able to try very experimental - features. - - Experimental features can be one of: - - working, in which case you should tell me it is! - - buggy, in which case you could try patching and send me the result - - unfinished, in which case you could try hacking it and send me the result - - non-existant, in which case you could also try hacking it in and send me - the result - -config BROKEN - bool - prompt "Try broken stuff" - default n - depends on EXPERIMENTAL - help - Select this if you want to _debug_ broken stuff. - -config DEBUG_CT - bool - prompt "Debug crosstool-NG" - default n - help - Say 'y' here to get some debugging options - -if DEBUG_CT - -config DEBUG_CT_PAUSE_STEPS - bool - prompt "Pause between every steps" - default n - help - Say 'y' if you intend to attend the build, and want to investigate - the result of each steps before running the next one. - -config DEBUG_CT_SAVE_STEPS - bool - prompt "Save intermediate steps" - default n - help - If you say 'y' here, then you will be able to restart crosstool-NG at - any step. - - It is not currently possible to restart at any of the debug facility. - They are treated as a whole. - - See docs/overview.txt for the list of steps. - -config DEBUG_CT_SAVE_STEPS_GZIP - bool - prompt "gzip saved states" - default y - depends on DEBUG_CT_SAVE_STEPS - help - If you are tight on space, then you can ask to gzip the saved states - tarballs. On the other hand, this takes some longer time... - - To lose as less time as possible, the gzip process is done with a low - compression ratio (-3), which gives roughly 70% gain in size. Going - further doesn't gain much, and takes far more time (believe me, I've - got figures here! :-) ). - -endif diff --git a/config/download_extract.in b/config/download_extract.in deleted file mode 100644 index 08b66ce..0000000 --- a/config/download_extract.in +++ /dev/null @@ -1,171 +0,0 @@ -# Options specific to downloading and extracting packages - -comment "Downloading" - -config FORCE_DOWNLOAD - bool - prompt "Force downloads" - default n - help - Force downloading tarballs, even if one already exists. - - Usefull if you suspect a tarball to be damaged. - -config ONLY_DOWNLOAD - bool - prompt "Stop after downloading tarballs" - default n - help - Only download the tarballs. Exit once it done. - - Usefull to pre-retrieve the tarballs before going off-line. - -choice - bool - prompt "Proxy type" - default USE_NO_PROXY - -config PROXY_TYPE_NONE - bool - prompt "No proxy" - help - Select this option if you have a direct connection to the internet, - or if you already set the environment adequately. - -config PROXY_TYPE_HTTP - bool - prompt "HTTP proxy" - help - Use an HTTP proxy to connect to to the internet. - Only the http and ftp protocols will be tunneled through this - proxy. - - Alternatively to setting this option, you can set and export the - following variables in your environment: - ftp_proxy=http://user:passwd@proxy.server:port/ - http_proxy=http://user:passwd@proxy.server:port/ - https_proxy=http://user:passwd@proxy.server:port/ - -# Haha! Here is an interesting feature/bug of mconf! -# The following config entries will be shown out-side the -# choice menu! -# To add a third entry in the choice menu, add it after the -# if...endif conditional below, and so on for a fourth entry... -if PROXY_TYPE_HTTP - -config PROXY_HOST - string - prompt "hostname/IP" - -config PROXY_PORT - int - prompt "port" - default 0 - -config PROXY_USER - string - prompt "user name" - -config PROXY_PASS - string - prompt "password" - -endif # USE_HTTP_PROXY - -config PROXY_TYPE_SOCKS - bool - prompt "SOCKS 4/5 proxy" - help - Use a Socks 4/5 proxy to connect to the internet. - All protocols can get tunneled through this kind of proxy (depending - on your proxy configuration, so;e do not allow all protocols, but - chances are that protocols needed by crosstool-NG are allowed). - - Alternatively to setting this option, you can set and export the - following variable in your environment: - LD_PRELOAD=/path/to/your/tsocks-library.so - - In any case, wether you set this option or you export the aforementionned - variable, you will _have_ to configure the /etc/tsocks.conf file - accordingly to your network setup. - - This option makes use of the tsocks library. You will have to have tsocks - installed on your system, of course. - - If you think you do not know what tsocks is, or how to configure it, - chances are that you do not need to set this option. - -if PROXY_TYPE_SOCKS - -choice - bool - prompt "type" - default PROXY_TYPE_SOCKS_5 - -config PROXY_TYPE_SOCKS_5 - bool - prompt "SOCKS 5" - -config PROXY_TYPE_SOCKS_4 - bool - prompt "SOCKS 4" - -endchoice - -config PROXY_HOST - string - prompt "hostname/IP" - -config PROXY_PORT - int - prompt "port" - default 0 - -config PROXY_USER - string - prompt "user name" - -config PROXY_PASS - string - prompt "password" - -endif # USE_SOCKS_PROXY - -endchoice - -config PROXY_TYPE - string - default "none" if PROXY_TYPE_NONE - default "HTTP" if PROXY_TYPE_HTTP - default "socks5" if PROXY_TYPE_SOCKS_5 - default "socks4" if PROXY_TYPE_SOCKS_4 - -# Force restore indentation -config BREAK_INDENT - bool - default n - -if ! ONLY_DOWNLOAD - -comment "Extracting" - -config FORCE_EXTRACT - bool - prompt "Force extractions" - default n - help - Force extraction of already exctracted tarballs. - - Usefull if you suspect a previous extract did not complete (eg. broken - tarball), or you added a new set of patches for this component. - -config ONLY_EXTRACT - bool - prompt "Stop after extracting tarballs" - default n - help - Exit after unpacking and patching tarballs. - - Usefull to look at the code before doing the build itself. - -endif # ! ONLY_DOWNLOAD diff --git a/config/global.in b/config/global.in index 1a02dba..82617a5 100644 --- a/config/global.in +++ b/config/global.in @@ -2,10 +2,10 @@ menu "Paths and misc options" -source "config/ct-behave.in" -source "config/download_extract.in" -source "config/build-behave.in" -source "config/paths.in" -source "config/logging.in" +source "config/global/ct-behave.in" +source "config/global/download_extract.in" +source "config/global/build-behave.in" +source "config/global/paths.in" +source "config/global/logging.in" endmenu diff --git a/config/global/build-behave.in b/config/global/build-behave.in new file mode 100644 index 0000000..7c1175c --- /dev/null +++ b/config/global/build-behave.in @@ -0,0 +1,45 @@ +# Options related to how the build behaves + +comment "Build behavior" + +config PARALLEL_JOBS + int + prompt "Number of parallel jobs" + default 1 + help + Number of jobs make will be allowed to run concurently. + Set this higher than the number of processors you have, but not too high. + A good rule of thumb is twice the number of processors you have. + + Enter 1 (or 0) to have only one job at a time. + +config LOAD + int + prompt "Maximum allowed load" + default 0 + help + Specifies that no new jobs should be started if there are others jobs + running and the load average is at least this value. + + Makes sense on SMP machines only. + + Enter 0 to have no limit on the load average. + + Note: only the integer part of the load is allowed here (you can't enter + 0.75 for example). + +config NICE + int + prompt "Nice level" + default 0 + range 0 19 + help + Renices the build process up. + +config USE_PIPES + bool + prompt "Use -pipe" + default y + help + Use gcc's option -pipe to use pipes rather than temp files when building + the toolchain. diff --git a/config/global/ct-behave.in b/config/global/ct-behave.in new file mode 100644 index 0000000..737028b --- /dev/null +++ b/config/global/ct-behave.in @@ -0,0 +1,82 @@ +# Options specific to crosstool-NG overall behavior + +comment "crosstool-NG behavior" + +config OBSOLETE + bool + prompt "Use obsolete features" + default n + help + If you set this to Y, you will be able to select obsolete features. + + Such obsolete features are the use of old kernel headers, old + gcc versions, etc... + +config EXPERIMENTAL + bool + prompt "Try features marked as EXPERIMENTAL" + default n + help + If you set this to Y, then you will be able to try very experimental + features. + + Experimental features can be one of: + - working, in which case you should tell me it is! + - buggy, in which case you could try patching and send me the result + - unfinished, in which case you could try hacking it and send me the result + - non-existant, in which case you could also try hacking it in and send me + the result + +config BROKEN + bool + prompt "Try broken stuff" + default n + depends on EXPERIMENTAL + help + Select this if you want to _debug_ broken stuff. + +config DEBUG_CT + bool + prompt "Debug crosstool-NG" + default n + help + Say 'y' here to get some debugging options + +if DEBUG_CT + +config DEBUG_CT_PAUSE_STEPS + bool + prompt "Pause between every steps" + default n + help + Say 'y' if you intend to attend the build, and want to investigate + the result of each steps before running the next one. + +config DEBUG_CT_SAVE_STEPS + bool + prompt "Save intermediate steps" + default n + help + If you say 'y' here, then you will be able to restart crosstool-NG at + any step. + + It is not currently possible to restart at any of the debug facility. + They are treated as a whole. + + See docs/overview.txt for the list of steps. + +config DEBUG_CT_SAVE_STEPS_GZIP + bool + prompt "gzip saved states" + default y + depends on DEBUG_CT_SAVE_STEPS + help + If you are tight on space, then you can ask to gzip the saved states + tarballs. On the other hand, this takes some longer time... + + To lose as less time as possible, the gzip process is done with a low + compression ratio (-3), which gives roughly 70% gain in size. Going + further doesn't gain much, and takes far more time (believe me, I've + got figures here! :-) ). + +endif diff --git a/config/global/download_extract.in b/config/global/download_extract.in new file mode 100644 index 0000000..08b66ce --- /dev/null +++ b/config/global/download_extract.in @@ -0,0 +1,171 @@ +# Options specific to downloading and extracting packages + +comment "Downloading" + +config FORCE_DOWNLOAD + bool + prompt "Force downloads" + default n + help + Force downloading tarballs, even if one already exists. + + Usefull if you suspect a tarball to be damaged. + +config ONLY_DOWNLOAD + bool + prompt "Stop after downloading tarballs" + default n + help + Only download the tarballs. Exit once it done. + + Usefull to pre-retrieve the tarballs before going off-line. + +choice + bool + prompt "Proxy type" + default USE_NO_PROXY + +config PROXY_TYPE_NONE + bool + prompt "No proxy" + help + Select this option if you have a direct connection to the internet, + or if you already set the environment adequately. + +config PROXY_TYPE_HTTP + bool + prompt "HTTP proxy" + help + Use an HTTP proxy to connect to to the internet. + Only the http and ftp protocols will be tunneled through this + proxy. + + Alternatively to setting this option, you can set and export the + following variables in your environment: + ftp_proxy=http://user:passwd@proxy.server:port/ + http_proxy=http://user:passwd@proxy.server:port/ + https_proxy=http://user:passwd@proxy.server:port/ + +# Haha! Here is an interesting feature/bug of mconf! +# The following config entries will be shown out-side the +# choice menu! +# To add a third entry in the choice menu, add it after the +# if...endif conditional below, and so on for a fourth entry... +if PROXY_TYPE_HTTP + +config PROXY_HOST + string + prompt "hostname/IP" + +config PROXY_PORT + int + prompt "port" + default 0 + +config PROXY_USER + string + prompt "user name" + +config PROXY_PASS + string + prompt "password" + +endif # USE_HTTP_PROXY + +config PROXY_TYPE_SOCKS + bool + prompt "SOCKS 4/5 proxy" + help + Use a Socks 4/5 proxy to connect to the internet. + All protocols can get tunneled through this kind of proxy (depending + on your proxy configuration, so;e do not allow all protocols, but + chances are that protocols needed by crosstool-NG are allowed). + + Alternatively to setting this option, you can set and export the + following variable in your environment: + LD_PRELOAD=/path/to/your/tsocks-library.so + + In any case, wether you set this option or you export the aforementionned + variable, you will _have_ to configure the /etc/tsocks.conf file + accordingly to your network setup. + + This option makes use of the tsocks library. You will have to have tsocks + installed on your system, of course. + + If you think you do not know what tsocks is, or how to configure it, + chances are that you do not need to set this option. + +if PROXY_TYPE_SOCKS + +choice + bool + prompt "type" + default PROXY_TYPE_SOCKS_5 + +config PROXY_TYPE_SOCKS_5 + bool + prompt "SOCKS 5" + +config PROXY_TYPE_SOCKS_4 + bool + prompt "SOCKS 4" + +endchoice + +config PROXY_HOST + string + prompt "hostname/IP" + +config PROXY_PORT + int + prompt "port" + default 0 + +config PROXY_USER + string + prompt "user name" + +config PROXY_PASS + string + prompt "password" + +endif # USE_SOCKS_PROXY + +endchoice + +config PROXY_TYPE + string + default "none" if PROXY_TYPE_NONE + default "HTTP" if PROXY_TYPE_HTTP + default "socks5" if PROXY_TYPE_SOCKS_5 + default "socks4" if PROXY_TYPE_SOCKS_4 + +# Force restore indentation +config BREAK_INDENT + bool + default n + +if ! ONLY_DOWNLOAD + +comment "Extracting" + +config FORCE_EXTRACT + bool + prompt "Force extractions" + default n + help + Force extraction of already exctracted tarballs. + + Usefull if you suspect a previous extract did not complete (eg. broken + tarball), or you added a new set of patches for this component. + +config ONLY_EXTRACT + bool + prompt "Stop after extracting tarballs" + default n + help + Exit after unpacking and patching tarballs. + + Usefull to look at the code before doing the build itself. + +endif # ! ONLY_DOWNLOAD diff --git a/config/global/logging.in b/config/global/logging.in new file mode 100644 index 0000000..49cda1f --- /dev/null +++ b/config/global/logging.in @@ -0,0 +1,110 @@ +# Options specific to logging + +comment "Logging" + +choice + bool + prompt "Maximum log level to see:" + default LOG_INFO if !DEBUG_CT + default LOG_DEBUG if DEBUG_CT + +config LOG_ERROR + bool + prompt "ERROR" + help + The build will be silent. + Only if there is an error will you see a message. + +config LOG_WARN + bool + prompt "WARN" + help + The same as above, plus warnings. + +config LOG_INFO + bool + prompt "INFO" + help + The same as above, plus informational messages (main steps). + +config LOG_EXTRA + bool + prompt "EXTRA" + help + The same as above, plus extra messages (sub-steps). + +config LOG_DEBUG + bool + prompt "DEBUG" + help + The same as above, plus lots of crosstool-NG debug information. + +config LOG_ALL + bool + prompt "ALL" + help + The same as above, plus all components build messages (very noisy!). + +endchoice + +config LOG_LEVEL_MAX + string + default "ERROR" if LOG_ERROR + default "WARN" if LOG_WARN + default "INFO" if LOG_INFO + default "EXTRA" if LOG_EXTRA + default "DEBUG" if LOG_DEBUG + default "ALL" if LOG_ALL + +config LOG_SEE_TOOLS_WARN + bool + prompt "Warnings from the tools' builds" + default n + depends on ! LOG_ERROR + help + Treat warnings from the different tools as crosstool-NG warnings. + If you say 'y' here, then those warnings will be prefixed with + '[WARN ]' instead of the default '[ALL ]'. + + You can safely say 'n' here. Those warnings will anyway be + recorded in the log file (provided you configured one). + + Tools error will always be logged as crosstool-NG errors. + +config LOG_PROGRESS_BAR + bool + prompt "Progress bar" + default y + depends on ! LOG_ALL + help + If you say 'y' here, you'll be able to see the elapsed time. + + As a bonus, you'll also get a rotating bar (/-\|) showing you + that the build is not stalled (the bar rotates 1/4 every 10 lines + of components build log). + + Note that the elapsed time can stall for a little while if a + component has long commands, as the elapsed time is only updated + each line. + +config LOG_TO_FILE + bool + prompt "Log to a file" + default y + help + Save *full* logs to a file. Even log levels you didn't specify above + will be available in this file. The log file will be named build.log + and stored in the toolchain prefix dir (set above). + + As a bonus, there is a script in tools/extractConfig.sh that is able + to extract the configuration of crosstool-NG from the log file. + + Definitely, say Y. + +config LOG_FILE_COMPRESS + bool + prompt "Compress the log file" + default n + depends on LOG_TO_FILE + help + Compress the log file once the toolchain is successfully built. diff --git a/config/global/paths.in b/config/global/paths.in new file mode 100644 index 0000000..3736d66 --- /dev/null +++ b/config/global/paths.in @@ -0,0 +1,89 @@ +# Options related to paths and install + +comment "Paths" + +config LOCAL_TARBALLS_DIR + string + prompt "Local tarballs directory" + default "" + help + If you have previously downloaded the tarballs, enter the PATH where + you stored them here. + +config SAVE_TARBALLS + bool + prompt "Save new tarballs" + default n + depends on LOCAL_TARBALLS_DIR != "" + help + If you say 'y' here, new downloaded tarballs will be saved in the + directory you entered above. + +config PREFIX_DIR + string + prompt "Prefix directory" + default "${HOME}/${CT_TARGET}" + help + This is the path the toolchain will run from. + +config INSTALL_DIR + string +# prompt "Install directory" + default "${CT_PREFIX_DIR}" +# help +# This is the path the target will be installed into. +# +# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons +# you can't write there, you can install somewhere else and have a third +# person do the install for you. +# The reason you might also want to install elsewhere is if you are going +# to package your shinny new toolchain for distribution. + +config CUSTOM_PATCH + bool + prompt "Use custom patch directory" + default n + help + If you have custom patches that you want to be applied, say 'Y' here and + enter the path directory below. + + Note that you must ensure that the patch directory is arranged the same + way the official directory is. + +config CUSTOM_PATCH_ONLY + bool + prompt "Only use custom patches" + default n + depends on CUSTOM_PATCH + help + Don't apply patches coming with crosstool-NG, only those patches available + in the directory below. + + If you say 'N' here, then the patches provided with crosstool-NG will be + applied first, and then your patches. + +config CUSTOM_PATCH_DIR + string + prompt "Custom patch directory" + default "" + depends on CUSTOM_PATCH + help + Enter the custom patch directory here. + +config REMOVE_DOCS + bool + prompt "Remove documentation" + default n + help + Remove the installed documentation (man and info pages). + Gains around 8MiB for a uClibc-based, C and C++ compiler. + +config INSTALL_DIR_RO + bool + prompt "Render the toolchain read-only" + default n + help + Render the directory of the toolchain (and its sub-directories) + read-only. + + Usefull for toolchains destined for production. diff --git a/config/kernel.in b/config/kernel.in index 2eaf4e3..2810776 100644 --- a/config/kernel.in +++ b/config/kernel.in @@ -19,7 +19,7 @@ config KERNEL_VERSION string if KERNEL_LINUX -source config/kernel_linux.in +source config/kernel/kernel_linux.in endif endmenu diff --git a/config/kernel/kernel_linux.in b/config/kernel/kernel_linux.in new file mode 100644 index 0000000..cb5348e --- /dev/null +++ b/config/kernel/kernel_linux.in @@ -0,0 +1,134 @@ +# Linux kernel options + +choice + bool + prompt "Get kernel headers from:" + +config KERNEL_LINUX_HEADERS_INSTALL + bool + prompt "kernel's 'headers_install'" + help + This will make use of the new headers_install rule in recent kernels. + This is most probably what you want to use. + +config KERNEL_LINUX_HEADERS_SANITISED + bool + prompt "Mazur's sanitized headers (OBSOLETE)" + depends on OBSOLETE + select KERNEL_LINUX_NEEDS_CONFIG + help + M. Mazur used to maintain a tree of sanitised headers, but it is now + obsoleted by the headers_install rule (above), and has not seen any + update since 2.6.12 + +config KERNEL_LINUX_HEADERS_COPY + bool + prompt "pure kernel headers (REALLY OBSOLETE)" + depends on OBSOLETE + select KERNEL_LINUX_NEEDS_CONFIG + help + This will simply copy the kernel headers to the toolchain. + + You do NOT want this. It's badly broken because it leaks kernel internals + to userspace. + +config KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR + bool + prompt "Use custom directory" + help + If you have some kernel headers lying around, you can enter the path + below. + +endchoice + +config KERNEL + string + default "linux" if ! KERNEL_LINUX_HEADERS_SANITISED + default "linux-libc-headers" if KERNEL_LINUX_HEADERS_SANITISED + +config KERNEL_VERSION_SEE_EXTRAVERSION + bool + prompt "See extra versions" + default n + depends on KERNEL_LINUX_HEADERS_COPY || KERNEL_LINUX_HEADERS_INSTALL + help + See extra versions (kernel with 4 numbers, eg 2.6.19.1). + + If you say 'no', you'll only see sub-level, 3-digit versions. + If you say 'yes', you'll see far more versions! + + It is recommended that you say 'no', unless you _*know*_ + that an extra version fixes a headers bug. + +if KERNEL_LINUX_HEADERS_INSTALL +source config/kernel/kernel_linux_headers_install.in +endif + +if KERNEL_LINUX_HEADERS_COPY +source config/kernel/kernel_linux_headers_copy.in +endif + +if KERNEL_LINUX_HEADERS_SANITISED +source config/kernel/kernel_linux_headers_sanitised.in +endif + +config KERNEL_LINUX_HEADERS_CUSTOM_DIR + string + prompt "Where are those custom headers?" + depends on KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR + help + Enter the base directory where the headers are to be found. + + Eg. if the headers are in /some/place/include, then enter /some/place. + This is the same path you entered when you typed: + make INSTALL_HDR_PATH=/some/place headers_install + +if ! KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR + +choice + bool + prompt "Kernel verbosity:" + default KERNEL_LINUX_VERBOSITY_0 + +config KERNEL_LINUX_VERBOSITY_0 + bool + prompt "Simplified" + help + Print simplified command lines. + +config KERNEL_LINUX_VERBOSITY_1 + bool + prompt "Full commands" + help + Print full command lines. + +config KERNEL_LINUX_VERBOSITY_2 + bool + prompt "Exec reasons" + help + Print the reasons why a make target is rebuild. + +endchoice + +config KERNEL_LINUX_VERBOSE_LEVEL + int + default 0 if KERNEL_LINUX_VERBOSITY_0 + default 1 if KERNEL_LINUX_VERBOSITY_1 + default 2 if KERNEL_LINUX_VERBOSITY_2 + +config KERNEL_LINUX_NEEDS_CONFIG + bool + default n + +config KERNEL_LINUX_CONFIG_FILE + string + prompt "Configuration file" + depends on KERNEL_LINUX_NEEDS_CONFIG + default "" + help + Path to a kernel configuration file. + + If you don't provide one, then the default configuration for + your target will be used. + +endif diff --git a/config/kernel/kernel_linux_headers_copy.in b/config/kernel/kernel_linux_headers_copy.in new file mode 100644 index 0000000..54eb700 --- /dev/null +++ b/config/kernel/kernel_linux_headers_copy.in @@ -0,0 +1,42 @@ +choice + bool + prompt "Linux kernel version" + +config KERNEL_COPY_V_2_4_26 + bool + prompt "2.4.26" + +config KERNEL_COPY_V_2_6_5 + bool + prompt "2.6.5" + +config KERNEL_COPY_V_2_6_6 + bool + prompt "2.6.6" + +config KERNEL_COPY_V_2_6_7 + bool + prompt "2.6.7" + +config KERNEL_COPY_V_2_6_8 + bool + prompt "2.6.8" + +config KERNEL_COPY_V_2_6_11_3 + bool + prompt "2.6.11.3" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +# CT_INSERT_VERSION_ABOVE +# Don't remove above line! +endchoice + +config KERNEL_VERSION + string + default "2.6.5" if KERNEL_COPY_V_2_6_5 + default "2.6.6" if KERNEL_COPY_V_2_6_6 + default "2.6.7" if KERNEL_COPY_V_2_6_7 + default "2.6.8" if KERNEL_COPY_V_2_6_8 + default "2.6.11.3" if KERNEL_COPY_V_2_6_11_3 +# CT_INSERT_VERSION_STRING_ABOVE +# Don't remove above line! diff --git a/config/kernel/kernel_linux_headers_install.in b/config/kernel/kernel_linux_headers_install.in new file mode 100644 index 0000000..60b471d --- /dev/null +++ b/config/kernel/kernel_linux_headers_install.in @@ -0,0 +1,168 @@ +choice + bool + prompt "Linux kernel version" + +config KERNEL_INSTALL_V_2_6_18_8 + bool + prompt "2.6.18.8 (OBSOLETE)" + depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE + +config KERNEL_INSTALL_V_2_6_19_7 + bool + prompt "2.6.19.7 (OBSOLETE)" + depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE + +config KERNEL_INSTALL_V_2_6_20_21 + bool + prompt "2.6.20.21 (OBSOLETE)" + depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE + +config KERNEL_INSTALL_V_2_6_21_7 + bool + prompt "2.6.21.7 (OBSOLETE)" + depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE + +config KERNEL_INSTALL_V_2_6_22_18 + bool + prompt "2.6.22.18" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23 + bool + prompt "2.6.23" + +config KERNEL_INSTALL_V_2_6_23_1 + bool + prompt "2.6.23.1" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_2 + bool + prompt "2.6.23.2" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_3 + bool + prompt "2.6.23.3" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_4 + bool + prompt "2.6.23.4" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_5 + bool + prompt "2.6.23.5" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_6 + bool + prompt "2.6.23.6" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_7 + bool + prompt "2.6.23.7" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_8 + bool + prompt "2.6.23.8" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_9 + bool + prompt "2.6.23.9" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_10 + bool + prompt "2.6.23.10" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_11 + bool + prompt "2.6.23.11" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_12 + bool + prompt "2.6.23.12" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_13 + bool + prompt "2.6.23.13" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_14 + bool + prompt "2.6.23.14" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_15 + bool + prompt "2.6.23.15" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_23_16 + bool + prompt "2.6.23.16" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_24 + bool + prompt "2.6.24" + +config KERNEL_INSTALL_V_2_6_24_1 + bool + prompt "2.6.24.1" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +config KERNEL_INSTALL_V_2_6_24_2 + bool + prompt "2.6.24.2" + depends on KERNEL_VERSION_SEE_EXTRAVERSION + +# CT_INSERT_VERSION_ABOVE +# Don't remove above line! +endchoice + +config KERNEL_VERSION + string + default "2.6.18.8" if KERNEL_INSTALL_V_2_6_18_8 + default "2.6.19.7" if KERNEL_INSTALL_V_2_6_19_7 + default "2.6.20.21" if KERNEL_INSTALL_V_2_6_20_21 + default "2.6.21.7" if KERNEL_INSTALL_V_2_6_21_7 + default "2.6.22.18" if KERNEL_INSTALL_V_2_6_22_18 + default "2.6.23" if KERNEL_INSTALL_V_2_6_23 + default "2.6.23.1" if KERNEL_INSTALL_V_2_6_23_1 + default "2.6.23.2" if KERNEL_INSTALL_V_2_6_23_2 + default "2.6.23.3" if KERNEL_INSTALL_V_2_6_23_3 + default "2.6.23.4" if KERNEL_INSTALL_V_2_6_23_4 + default "2.6.23.5" if KERNEL_INSTALL_V_2_6_23_5 + default "2.6.23.6" if KERNEL_INSTALL_V_2_6_23_6 + default "2.6.23.7" if KERNEL_INSTALL_V_2_6_23_7 + default "2.6.23.8" if KERNEL_INSTALL_V_2_6_23_8 + default "2.6.23.9" if KERNEL_INSTALL_V_2_6_23_9 + default "2.6.23.10" if KERNEL_INSTALL_V_2_6_23_10 + default "2.6.23.11" if KERNEL_INSTALL_V_2_6_23_11 + default "2.6.23.12" if KERNEL_INSTALL_V_2_6_23_12 + default "2.6.23.13" if KERNEL_INSTALL_V_2_6_23_13 + default "2.6.23.14" if KERNEL_INSTALL_V_2_6_23_14 + default "2.6.23.15" if KERNEL_INSTALL_V_2_6_23_15 + default "2.6.23.16" if KERNEL_INSTALL_V_2_6_23_16 + default "2.6.24" if KERNEL_INSTALL_V_2_6_24 + default "2.6.24.1" if KERNEL_INSTALL_V_2_6_24_1 + default "2.6.24.2" if KERNEL_INSTALL_V_2_6_24_2 +# CT_INSERT_VERSION_STRING_ABOVE +# Don't remove above line! + +config KERNEL_LINUX_HEADERS_INSTALL_CHECK + bool + prompt "Check installed headers" + default n + help + If you are in doubt that installed headers are buggy, say 'Y' + here to have an extra check passed onto the headers. diff --git a/config/kernel/kernel_linux_headers_sanitised.in b/config/kernel/kernel_linux_headers_sanitised.in new file mode 100644 index 0000000..820df6e --- /dev/null +++ b/config/kernel/kernel_linux_headers_sanitised.in @@ -0,0 +1,62 @@ +choice + bool + prompt "Linux headers version" + +config KERNEL_SANITISED_V_2_6_7_0 + bool + prompt "2.6.7.0" + +config KERNEL_SANITISED_V_2_6_8_0 + bool + prompt "2.6.8.0" + +config KERNEL_SANITISED_V_2_6_8_1 + bool + prompt "2.6.8.1" + +config KERNEL_SANITISED_V_2_6_9_0 + bool + prompt "2.6.9.0" + +config KERNEL_SANITISED_V_2_6_9_1 + bool + prompt "2.6.9.1" + +config KERNEL_SANITISED_V_2_6_10_0 + bool + prompt "2.6.10.0" + +config KERNEL_SANITISED_V_2_6_11_0 + bool + prompt "2.6.11.0" + +config KERNEL_SANITISED_V_2_6_11_1 + bool + prompt "2.6.11.1" + +config KERNEL_SANITISED_V_2_6_11_2 + bool + prompt "2.6.11.2" + +config KERNEL_SANITISED_V_2_6_12_0 + bool + prompt "2.6.12.0" + +# CT_INSERT_VERSION_ABOVE +# Don't remove above line! +endchoice + +config KERNEL_VERSION + string + default "2.6.7.0" if KERNEL_SANITISED_V_2_6_7_0 + default "2.6.8.0" if KERNEL_SANITISED_V_2_6_8_0 + default "2.6.8.1" if KERNEL_SANITISED_V_2_6_8_1 + default "2.6.9.0" if KERNEL_SANITISED_V_2_6_9_0 + default "2.6.9.1" if KERNEL_SANITISED_V_2_6_9_1 + default "2.6.10.0" if KERNEL_SANITISED_V_2_6_10_0 + default "2.6.11.0" if KERNEL_SANITISED_V_2_6_11_0 + default "2.6.11.1" if KERNEL_SANITISED_V_2_6_11_1 + default "2.6.11.2" if KERNEL_SANITISED_V_2_6_11_2 + default "2.6.12.0" if KERNEL_SANITISED_V_2_6_12_0 +# CT_INSERT_VERSION_STRING_ABOVE +# Don't remove above line! diff --git a/config/kernel_linux.in b/config/kernel_linux.in deleted file mode 100644 index 41f6307..0000000 --- a/config/kernel_linux.in +++ /dev/null @@ -1,134 +0,0 @@ -# Linux kernel options - -choice - bool - prompt "Get kernel headers from:" - -config KERNEL_LINUX_HEADERS_INSTALL - bool - prompt "kernel's 'headers_install'" - help - This will make use of the new headers_install rule in recent kernels. - This is most probably what you want to use. - -config KERNEL_LINUX_HEADERS_SANITISED - bool - prompt "Mazur's sanitized headers (OBSOLETE)" - depends on OBSOLETE - select KERNEL_LINUX_NEEDS_CONFIG - help - M. Mazur used to maintain a tree of sanitised headers, but it is now - obsoleted by the headers_install rule (above), and has not seen any - update since 2.6.12 - -config KERNEL_LINUX_HEADERS_COPY - bool - prompt "pure kernel headers (REALLY OBSOLETE)" - depends on OBSOLETE - select KERNEL_LINUX_NEEDS_CONFIG - help - This will simply copy the kernel headers to the toolchain. - - You do NOT want this. It's badly broken because it leaks kernel internals - to userspace. - -config KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR - bool - prompt "Use custom directory" - help - If you have some kernel headers lying around, you can enter the path - below. - -endchoice - -config KERNEL - string - default "linux" if ! KERNEL_LINUX_HEADERS_SANITISED - default "linux-libc-headers" if KERNEL_LINUX_HEADERS_SANITISED - -config KERNEL_VERSION_SEE_EXTRAVERSION - bool - prompt "See extra versions" - default n - depends on KERNEL_LINUX_HEADERS_COPY || KERNEL_LINUX_HEADERS_INSTALL - help - See extra versions (kernel with 4 numbers, eg 2.6.19.1). - - If you say 'no', you'll only see sub-level, 3-digit versions. - If you say 'yes', you'll see far more versions! - - It is recommended that you say 'no', unless you _*know*_ - that an extra version fixes a headers bug. - -if KERNEL_LINUX_HEADERS_INSTALL -source config/kernel_linux_headers_install.in -endif - -if KERNEL_LINUX_HEADERS_COPY -source config/kernel_linux_headers_copy.in -endif - -if KERNEL_LINUX_HEADERS_SANITISED -source config/kernel_linux_headers_sanitised.in -endif - -config KERNEL_LINUX_HEADERS_CUSTOM_DIR - string - prompt "Where are those custom headers?" - depends on KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR - help - Enter the base directory where the headers are to be found. - - Eg. if the headers are in /some/place/include, then enter /some/place. - This is the same path you entered when you typed: - make INSTALL_HDR_PATH=/some/place headers_install - -if ! KERNEL_LINUX_HEADERS_USE_CUSTOM_DIR - -choice - bool - prompt "Kernel verbosity:" - default KERNEL_LINUX_VERBOSITY_0 - -config KERNEL_LINUX_VERBOSITY_0 - bool - prompt "Simplified" - help - Print simplified command lines. - -config KERNEL_LINUX_VERBOSITY_1 - bool - prompt "Full commands" - help - Print full command lines. - -config KERNEL_LINUX_VERBOSITY_2 - bool - prompt "Exec reasons" - help - Print the reasons why a make target is rebuild. - -endchoice - -config KERNEL_LINUX_VERBOSE_LEVEL - int - default 0 if KERNEL_LINUX_VERBOSITY_0 - default 1 if KERNEL_LINUX_VERBOSITY_1 - default 2 if KERNEL_LINUX_VERBOSITY_2 - -config KERNEL_LINUX_NEEDS_CONFIG - bool - default n - -config KERNEL_LINUX_CONFIG_FILE - string - prompt "Configuration file" - depends on KERNEL_LINUX_NEEDS_CONFIG - default "" - help - Path to a kernel configuration file. - - If you don't provide one, then the default configuration for - your target will be used. - -endif diff --git a/config/kernel_linux_headers_copy.in b/config/kernel_linux_headers_copy.in deleted file mode 100644 index 54eb700..0000000 --- a/config/kernel_linux_headers_copy.in +++ /dev/null @@ -1,42 +0,0 @@ -choice - bool - prompt "Linux kernel version" - -config KERNEL_COPY_V_2_4_26 - bool - prompt "2.4.26" - -config KERNEL_COPY_V_2_6_5 - bool - prompt "2.6.5" - -config KERNEL_COPY_V_2_6_6 - bool - prompt "2.6.6" - -config KERNEL_COPY_V_2_6_7 - bool - prompt "2.6.7" - -config KERNEL_COPY_V_2_6_8 - bool - prompt "2.6.8" - -config KERNEL_COPY_V_2_6_11_3 - bool - prompt "2.6.11.3" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -# CT_INSERT_VERSION_ABOVE -# Don't remove above line! -endchoice - -config KERNEL_VERSION - string - default "2.6.5" if KERNEL_COPY_V_2_6_5 - default "2.6.6" if KERNEL_COPY_V_2_6_6 - default "2.6.7" if KERNEL_COPY_V_2_6_7 - default "2.6.8" if KERNEL_COPY_V_2_6_8 - default "2.6.11.3" if KERNEL_COPY_V_2_6_11_3 -# CT_INSERT_VERSION_STRING_ABOVE -# Don't remove above line! diff --git a/config/kernel_linux_headers_install.in b/config/kernel_linux_headers_install.in deleted file mode 100644 index 60b471d..0000000 --- a/config/kernel_linux_headers_install.in +++ /dev/null @@ -1,168 +0,0 @@ -choice - bool - prompt "Linux kernel version" - -config KERNEL_INSTALL_V_2_6_18_8 - bool - prompt "2.6.18.8 (OBSOLETE)" - depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE - -config KERNEL_INSTALL_V_2_6_19_7 - bool - prompt "2.6.19.7 (OBSOLETE)" - depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE - -config KERNEL_INSTALL_V_2_6_20_21 - bool - prompt "2.6.20.21 (OBSOLETE)" - depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE - -config KERNEL_INSTALL_V_2_6_21_7 - bool - prompt "2.6.21.7 (OBSOLETE)" - depends on KERNEL_VERSION_SEE_EXTRAVERSION && OBSOLETE - -config KERNEL_INSTALL_V_2_6_22_18 - bool - prompt "2.6.22.18" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23 - bool - prompt "2.6.23" - -config KERNEL_INSTALL_V_2_6_23_1 - bool - prompt "2.6.23.1" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_2 - bool - prompt "2.6.23.2" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_3 - bool - prompt "2.6.23.3" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_4 - bool - prompt "2.6.23.4" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_5 - bool - prompt "2.6.23.5" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_6 - bool - prompt "2.6.23.6" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_7 - bool - prompt "2.6.23.7" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_8 - bool - prompt "2.6.23.8" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_9 - bool - prompt "2.6.23.9" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_10 - bool - prompt "2.6.23.10" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_11 - bool - prompt "2.6.23.11" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_12 - bool - prompt "2.6.23.12" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_13 - bool - prompt "2.6.23.13" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_14 - bool - prompt "2.6.23.14" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_15 - bool - prompt "2.6.23.15" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_23_16 - bool - prompt "2.6.23.16" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_24 - bool - prompt "2.6.24" - -config KERNEL_INSTALL_V_2_6_24_1 - bool - prompt "2.6.24.1" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -config KERNEL_INSTALL_V_2_6_24_2 - bool - prompt "2.6.24.2" - depends on KERNEL_VERSION_SEE_EXTRAVERSION - -# CT_INSERT_VERSION_ABOVE -# Don't remove above line! -endchoice - -config KERNEL_VERSION - string - default "2.6.18.8" if KERNEL_INSTALL_V_2_6_18_8 - default "2.6.19.7" if KERNEL_INSTALL_V_2_6_19_7 - default "2.6.20.21" if KERNEL_INSTALL_V_2_6_20_21 - default "2.6.21.7" if KERNEL_INSTALL_V_2_6_21_7 - default "2.6.22.18" if KERNEL_INSTALL_V_2_6_22_18 - default "2.6.23" if KERNEL_INSTALL_V_2_6_23 - default "2.6.23.1" if KERNEL_INSTALL_V_2_6_23_1 - default "2.6.23.2" if KERNEL_INSTALL_V_2_6_23_2 - default "2.6.23.3" if KERNEL_INSTALL_V_2_6_23_3 - default "2.6.23.4" if KERNEL_INSTALL_V_2_6_23_4 - default "2.6.23.5" if KERNEL_INSTALL_V_2_6_23_5 - default "2.6.23.6" if KERNEL_INSTALL_V_2_6_23_6 - default "2.6.23.7" if KERNEL_INSTALL_V_2_6_23_7 - default "2.6.23.8" if KERNEL_INSTALL_V_2_6_23_8 - default "2.6.23.9" if KERNEL_INSTALL_V_2_6_23_9 - default "2.6.23.10" if KERNEL_INSTALL_V_2_6_23_10 - default "2.6.23.11" if KERNEL_INSTALL_V_2_6_23_11 - default "2.6.23.12" if KERNEL_INSTALL_V_2_6_23_12 - default "2.6.23.13" if KERNEL_INSTALL_V_2_6_23_13 - default "2.6.23.14" if KERNEL_INSTALL_V_2_6_23_14 - default "2.6.23.15" if KERNEL_INSTALL_V_2_6_23_15 - default "2.6.23.16" if KERNEL_INSTALL_V_2_6_23_16 - default "2.6.24" if KERNEL_INSTALL_V_2_6_24 - default "2.6.24.1" if KERNEL_INSTALL_V_2_6_24_1 - default "2.6.24.2" if KERNEL_INSTALL_V_2_6_24_2 -# CT_INSERT_VERSION_STRING_ABOVE -# Don't remove above line! - -config KERNEL_LINUX_HEADERS_INSTALL_CHECK - bool - prompt "Check installed headers" - default n - help - If you are in doubt that installed headers are buggy, say 'Y' - here to have an extra check passed onto the headers. diff --git a/config/kernel_linux_headers_sanitised.in b/config/kernel_linux_headers_sanitised.in deleted file mode 100644 index 820df6e..0000000 --- a/config/kernel_linux_headers_sanitised.in +++ /dev/null @@ -1,62 +0,0 @@ -choice - bool - prompt "Linux headers version" - -config KERNEL_SANITISED_V_2_6_7_0 - bool - prompt "2.6.7.0" - -config KERNEL_SANITISED_V_2_6_8_0 - bool - prompt "2.6.8.0" - -config KERNEL_SANITISED_V_2_6_8_1 - bool - prompt "2.6.8.1" - -config KERNEL_SANITISED_V_2_6_9_0 - bool - prompt "2.6.9.0" - -config KERNEL_SANITISED_V_2_6_9_1 - bool - prompt "2.6.9.1" - -config KERNEL_SANITISED_V_2_6_10_0 - bool - prompt "2.6.10.0" - -config KERNEL_SANITISED_V_2_6_11_0 - bool - prompt "2.6.11.0" - -config KERNEL_SANITISED_V_2_6_11_1 - bool - prompt "2.6.11.1" - -config KERNEL_SANITISED_V_2_6_11_2 - bool - prompt "2.6.11.2" - -config KERNEL_SANITISED_V_2_6_12_0 - bool - prompt "2.6.12.0" - -# CT_INSERT_VERSION_ABOVE -# Don't remove above line! -endchoice - -config KERNEL_VERSION - string - default "2.6.7.0" if KERNEL_SANITISED_V_2_6_7_0 - default "2.6.8.0" if KERNEL_SANITISED_V_2_6_8_0 - default "2.6.8.1" if KERNEL_SANITISED_V_2_6_8_1 - default "2.6.9.0" if KERNEL_SANITISED_V_2_6_9_0 - default "2.6.9.1" if KERNEL_SANITISED_V_2_6_9_1 - default "2.6.10.0" if KERNEL_SANITISED_V_2_6_10_0 - default "2.6.11.0" if KERNEL_SANITISED_V_2_6_11_0 - default "2.6.11.1" if KERNEL_SANITISED_V_2_6_11_1 - default "2.6.11.2" if KERNEL_SANITISED_V_2_6_11_2 - default "2.6.12.0" if KERNEL_SANITISED_V_2_6_12_0 -# CT_INSERT_VERSION_STRING_ABOVE -# Don't remove above line! diff --git a/config/libc.in b/config/libc.in index e919ba8..848a89c 100644 --- a/config/libc.in +++ b/config/libc.in @@ -37,11 +37,11 @@ config LIBC_SUPPORT_LINUXTHREADS default n if LIBC_GLIBC -source config/libc_glibc.in +source config/libc/libc_glibc.in endif if LIBC_UCLIBC -source config/libc_uClibc.in +source config/libc/libc_uClibc.in endif endmenu diff --git a/config/libc/libc_glibc.in b/config/libc/libc_glibc.in new file mode 100644 index 0000000..e4359b7 --- /dev/null +++ b/config/libc/libc_glibc.in @@ -0,0 +1,124 @@ +# glibc options + +choice + bool + prompt "glibc version" + +config LIBC_V_2_3_6 + bool + prompt "2.3.6 (OBSOLETE)" + depends on OBSOLETE + +config LIBC_V_2_5 + bool + prompt "2.5" + +config LIBC_V_2_5_1 + bool + prompt "2.5.1" + +config LIBC_V_2_6 + bool + prompt "2.6" + +config LIBC_V_2_6_1 + bool + prompt "2.6.1" + +config LIBC_V_2_7 + bool + prompt "2.7" + depends on EXPERIMENTAL + +# CT_INSERT_VERSION_ABOVE +# Don't remove above line! +endchoice + +config LIBC_VERSION + string + default "2.3.6" if LIBC_V_2_3_6 + default "2.4" if LIBC_V_2_4 + default "2.5" if LIBC_V_2_5 + default "2.5.1" if LIBC_V_2_5_1 + default "2.6" if LIBC_V_2_6 + default "2.6.1" if LIBC_V_2_6_1 + default "2.7" if LIBC_V_2_7 +# CT_INSERT_VERSION_STRING_ABOVE +# Don't remove above line! + +config LIBC_GLIBC_EXTRA_CONFIG + string + prompt "glibc extra config" + default "" + help + Extra flags to pass onto ./configure when configuring glibc. + + Eg.: --enable-static-nss + +config LIBC_GLIBC_EXTRA_CFLAGS + string + prompt "glibc extra target CFLAGS" + default "" + help + Extra target CFLAGS to use when building glibc. + +config LIBC_EXTRA_CC_ARGS + string + prompt "gcc extra flags" + default "" + help + Extra flags to pass gcc when building glibc. + + Seldom used, except for sparc64 which seems to need the flag -64 + to be passed onto gcc. + +# Please note: This is not used for now (no sh support). +config LIBC_GLIBC_CONFIGPARMS + string + prompt "Extra config params (READ HELP)" + default "" if ARCH != "sh3" && ARCH != "sh4" + default "no-z-defs=yes" if ARCH = "sh3" || ARCH = "sh4" + help + Some architectures need to set options in the file configparms. + This is the case for sh3/4, which really need to set configparms as of + gcc-3.4/glibc-2.3.2. + + Unless you are building a toolchain for sh3/4, you should leave that empty. + + Note: this is awkward, doesn't work well if you need more than one + line in configparms + +config LIBC_GLIBC_USE_PORTS + bool + prompt "Use the ports addon" + default n + help + The ports addon contains some architecture ports that are not available + in the official glibc distribution. + + For example, this is the case for ARM with glibc >= 2.4 + + Say n only if you're sure that your architecture is in the official + glibc distribution for your chosen version. + +config LIBC_ADDONS + bool + prompt "Pass extra addons list" + default n + help + If you say Y here, you'll be able to give the list of addons you want to + include in your C library. + +config LIBC_ADDONS_LIST + string + prompt "Extra addons" + default "" + depends on LIBC_ADDONS + help + Extra addons to include in glibc. Space separated list. + + You need to specify neither linuxthreads nor nptl, as they are added + automagically for you depending on the threading model you choosed + earlier. + + Eg.: crypt (for very old glibces) diff --git a/config/libc/libc_uClibc.in b/config/libc/libc_uClibc.in new file mode 100644 index 0000000..4f9943d --- /dev/null +++ b/config/libc/libc_uClibc.in @@ -0,0 +1,101 @@ +# uClibc options + +choice + bool + prompt "uClibc version" + +config LIBC_V_snapshot + bool + prompt "latest snapshot" + +config LIBC_V_specific_date + bool + prompt "" + +config LIBC_V_0_9_28 + bool + prompt "0.9.28 (OBSOLETE)" + depends on OBSOLETE + +config LIBC_V_0_9_28_1 + bool + prompt "0.9.28.1 (OBSOLETE)" + depends on OBSOLETE + +config LIBC_V_0_9_28_2 + bool + prompt "0.9.28.2 (OBSOLETE)" + depends on OBSOLETE + +config LIBC_V_0_9_28_3 + bool + prompt "0.9.28.3" + +config LIBC_V_0_9_29 + bool + prompt "0.9.29" + +# CT_INSERT_VERSION_ABOVE +# Don't remove above line! +endchoice + +config LIBC_VERSION + string + prompt "Enter date (YYYYMMDD)" if LIBC_V_specific_date + default "snapshot" if LIBC_V_snapshot + default "0.9.28" if LIBC_V_0_9_28 + default "0.9.28.1" if LIBC_V_0_9_28_1 + default "0.9.28.2" if LIBC_V_0_9_28_2 + default "0.9.28.3" if LIBC_V_0_9_28_3 + default "0.9.29" if LIBC_V_0_9_29 +# CT_INSERT_VERSION_STRING_ABOVE +# Don't remove above line! + help + Enter the date of the snapshot you want to use in the form: YYYYMMDD + where YYYY is the 4-digit year, MM the 2-digit month and DD the 2-digit + day in the month. + + Please note that uClibc site removes snapshots older than a month. + +choice + bool + prompt "Debug level" + default LIBC_UCLIBC_DEBUG_LEVEL_0 + +config LIBC_UCLIBC_DEBUG_LEVEL_0 + bool + prompt "none" + +config LIBC_UCLIBC_DEBUG_LEVEL_1 + bool + prompt "minimal" + +config LIBC_UCLIBC_DEBUG_LEVEL_2 + bool + prompt "all" + +endchoice + +config LIBC_UCLIBC_DEBUG_LEVEL + int + default 0 if LIBC_UCLIBC_DEBUG_LEVEL_0 + default 1 if LIBC_UCLIBC_DEBUG_LEVEL_1 + default 2 if LIBC_UCLIBC_DEBUG_LEVEL_2 + +config LIBC_UCLIBC_CONFIG_FILE + string + prompt "Configuration file" + default "" + help + Path to the configuration file. + + You _must_ provide one (for now). + +config LIBC_UCLIBC_LOCALES + bool + prompt "Add support for locales" + default n + help + Say y if you want uClibc to support localisation. + + Note that seems to be broken on recent uClibc releases. diff --git a/config/libc_glibc.in b/config/libc_glibc.in deleted file mode 100644 index e4359b7..0000000 --- a/config/libc_glibc.in +++ /dev/null @@ -1,124 +0,0 @@ -# glibc options - -choice - bool - prompt "glibc version" - -config LIBC_V_2_3_6 - bool - prompt "2.3.6 (OBSOLETE)" - depends on OBSOLETE - -config LIBC_V_2_5 - bool - prompt "2.5" - -config LIBC_V_2_5_1 - bool - prompt "2.5.1" - -config LIBC_V_2_6 - bool - prompt "2.6" - -config LIBC_V_2_6_1 - bool - prompt "2.6.1" - -config LIBC_V_2_7 - bool - prompt "2.7" - depends on EXPERIMENTAL - -# CT_INSERT_VERSION_ABOVE -# Don't remove above line! -endchoice - -config LIBC_VERSION - string - default "2.3.6" if LIBC_V_2_3_6 - default "2.4" if LIBC_V_2_4 - default "2.5" if LIBC_V_2_5 - default "2.5.1" if LIBC_V_2_5_1 - default "2.6" if LIBC_V_2_6 - default "2.6.1" if LIBC_V_2_6_1 - default "2.7" if LIBC_V_2_7 -# CT_INSERT_VERSION_STRING_ABOVE -# Don't remove above line! - -config LIBC_GLIBC_EXTRA_CONFIG - string - prompt "glibc extra config" - default "" - help - Extra flags to pass onto ./configure when configuring glibc. - - Eg.: --enable-static-nss - -config LIBC_GLIBC_EXTRA_CFLAGS - string - prompt "glibc extra target CFLAGS" - default "" - help - Extra target CFLAGS to use when building glibc. - -config LIBC_EXTRA_CC_ARGS - string - prompt "gcc extra flags" - default "" - help - Extra flags to pass gcc when building glibc. - - Seldom used, except for sparc64 which seems to need the flag -64 - to be passed onto gcc. - -# Please note: This is not used for now (no sh support). -config LIBC_GLIBC_CONFIGPARMS - string - prompt "Extra config params (READ HELP)" - default "" if ARCH != "sh3" && ARCH != "sh4" - default "no-z-defs=yes" if ARCH = "sh3" || ARCH = "sh4" - help - Some architectures need to set options in the file configparms. - This is the case for sh3/4, which really need to set configparms as of - gcc-3.4/glibc-2.3.2. - - Unless you are building a toolchain for sh3/4, you should leave that empty. - - Note: this is awkward, doesn't work well if you need more than one - line in configparms - -config LIBC_GLIBC_USE_PORTS - bool - prompt "Use the ports addon" - default n - help - The ports addon contains some architecture ports that are not available - in the official glibc distribution. - - For example, this is the case for ARM with glibc >= 2.4 - - Say n only if you're sure that your architecture is in the official - glibc distribution for your chosen version. - -config LIBC_ADDONS - bool - prompt "Pass extra addons list" - default n - help - If you say Y here, you'll be able to give the list of addons you want to - include in your C library. - -config LIBC_ADDONS_LIST - string - prompt "Extra addons" - default "" - depends on LIBC_ADDONS - help - Extra addons to include in glibc. Space separated list. - - You need to specify neither linuxthreads nor nptl, as they are added - automagically for you depending on the threading model you choosed - earlier. - - Eg.: crypt (for very old glibces) diff --git a/config/libc_uClibc.in b/config/libc_uClibc.in deleted file mode 100644 index 4f9943d..0000000 --- a/config/libc_uClibc.in +++ /dev/null @@ -1,101 +0,0 @@ -# uClibc options - -choice - bool - prompt "uClibc version" - -config LIBC_V_snapshot - bool - prompt "latest snapshot" - -config LIBC_V_specific_date - bool - prompt "" - -config LIBC_V_0_9_28 - bool - prompt "0.9.28 (OBSOLETE)" - depends on OBSOLETE - -config LIBC_V_0_9_28_1 - bool - prompt "0.9.28.1 (OBSOLETE)" - depends on OBSOLETE - -config LIBC_V_0_9_28_2 - bool - prompt "0.9.28.2 (OBSOLETE)" - depends on OBSOLETE - -config LIBC_V_0_9_28_3 - bool - prompt "0.9.28.3" - -config LIBC_V_0_9_29 - bool - prompt "0.9.29" - -# CT_INSERT_VERSION_ABOVE -# Don't remove above line! -endchoice - -config LIBC_VERSION - string - prompt "Enter date (YYYYMMDD)" if LIBC_V_specific_date - default "snapshot" if LIBC_V_snapshot - default "0.9.28" if LIBC_V_0_9_28 - default "0.9.28.1" if LIBC_V_0_9_28_1 - default "0.9.28.2" if LIBC_V_0_9_28_2 - default "0.9.28.3" if LIBC_V_0_9_28_3 - default "0.9.29" if LIBC_V_0_9_29 -# CT_INSERT_VERSION_STRING_ABOVE -# Don't remove above line! - help - Enter the date of the snapshot you want to use in the form: YYYYMMDD - where YYYY is the 4-digit year, MM the 2-digit month and DD the 2-digit - day in the month. - - Please note that uClibc site removes snapshots older than a month. - -choice - bool - prompt "Debug level" - default LIBC_UCLIBC_DEBUG_LEVEL_0 - -config LIBC_UCLIBC_DEBUG_LEVEL_0 - bool - prompt "none" - -config LIBC_UCLIBC_DEBUG_LEVEL_1 - bool - prompt "minimal" - -config LIBC_UCLIBC_DEBUG_LEVEL_2 - bool - prompt "all" - -endchoice - -config LIBC_UCLIBC_DEBUG_LEVEL - int - default 0 if LIBC_UCLIBC_DEBUG_LEVEL_0 - default 1 if LIBC_UCLIBC_DEBUG_LEVEL_1 - default 2 if LIBC_UCLIBC_DEBUG_LEVEL_2 - -config LIBC_UCLIBC_CONFIG_FILE - string - prompt "Configuration file" - default "" - help - Path to the configuration file. - - You _must_ provide one (for now). - -config LIBC_UCLIBC_LOCALES - bool - prompt "Add support for locales" - default n - help - Say y if you want uClibc to support localisation. - - Note that seems to be broken on recent uClibc releases. diff --git a/config/logging.in b/config/logging.in deleted file mode 100644 index 49cda1f..0000000 --- a/config/logging.in +++ /dev/null @@ -1,110 +0,0 @@ -# Options specific to logging - -comment "Logging" - -choice - bool - prompt "Maximum log level to see:" - default LOG_INFO if !DEBUG_CT - default LOG_DEBUG if DEBUG_CT - -config LOG_ERROR - bool - prompt "ERROR" - help - The build will be silent. - Only if there is an error will you see a message. - -config LOG_WARN - bool - prompt "WARN" - help - The same as above, plus warnings. - -config LOG_INFO - bool - prompt "INFO" - help - The same as above, plus informational messages (main steps). - -config LOG_EXTRA - bool - prompt "EXTRA" - help - The same as above, plus extra messages (sub-steps). - -config LOG_DEBUG - bool - prompt "DEBUG" - help - The same as above, plus lots of crosstool-NG debug information. - -config LOG_ALL - bool - prompt "ALL" - help - The same as above, plus all components build messages (very noisy!). - -endchoice - -config LOG_LEVEL_MAX - string - default "ERROR" if LOG_ERROR - default "WARN" if LOG_WARN - default "INFO" if LOG_INFO - default "EXTRA" if LOG_EXTRA - default "DEBUG" if LOG_DEBUG - default "ALL" if LOG_ALL - -config LOG_SEE_TOOLS_WARN - bool - prompt "Warnings from the tools' builds" - default n - depends on ! LOG_ERROR - help - Treat warnings from the different tools as crosstool-NG warnings. - If you say 'y' here, then those warnings will be prefixed with - '[WARN ]' instead of the default '[ALL ]'. - - You can safely say 'n' here. Those warnings will anyway be - recorded in the log file (provided you configured one). - - Tools error will always be logged as crosstool-NG errors. - -config LOG_PROGRESS_BAR - bool - prompt "Progress bar" - default y - depends on ! LOG_ALL - help - If you say 'y' here, you'll be able to see the elapsed time. - - As a bonus, you'll also get a rotating bar (/-\|) showing you - that the build is not stalled (the bar rotates 1/4 every 10 lines - of components build log). - - Note that the elapsed time can stall for a little while if a - component has long commands, as the elapsed time is only updated - each line. - -config LOG_TO_FILE - bool - prompt "Log to a file" - default y - help - Save *full* logs to a file. Even log levels you didn't specify above - will be available in this file. The log file will be named build.log - and stored in the toolchain prefix dir (set above). - - As a bonus, there is a script in tools/extractConfig.sh that is able - to extract the configuration of crosstool-NG from the log file. - - Definitely, say Y. - -config LOG_FILE_COMPRESS - bool - prompt "Compress the log file" - default n - depends on LOG_TO_FILE - help - Compress the log file once the toolchain is successfully built. diff --git a/config/paths.in b/config/paths.in deleted file mode 100644 index 3736d66..0000000 --- a/config/paths.in +++ /dev/null @@ -1,89 +0,0 @@ -# Options related to paths and install - -comment "Paths" - -config LOCAL_TARBALLS_DIR - string - prompt "Local tarballs directory" - default "" - help - If you have previously downloaded the tarballs, enter the PATH where - you stored them here. - -config SAVE_TARBALLS - bool - prompt "Save new tarballs" - default n - depends on LOCAL_TARBALLS_DIR != "" - help - If you say 'y' here, new downloaded tarballs will be saved in the - directory you entered above. - -config PREFIX_DIR - string - prompt "Prefix directory" - default "${HOME}/${CT_TARGET}" - help - This is the path the toolchain will run from. - -config INSTALL_DIR - string -# prompt "Install directory" - default "${CT_PREFIX_DIR}" -# help -# This is the path the target will be installed into. -# -# Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons -# you can't write there, you can install somewhere else and have a third -# person do the install for you. -# The reason you might also want to install elsewhere is if you are going -# to package your shinny new toolchain for distribution. - -config CUSTOM_PATCH - bool - prompt "Use custom patch directory" - default n - help - If you have custom patches that you want to be applied, say 'Y' here and - enter the path directory below. - - Note that you must ensure that the patch directory is arranged the same - way the official directory is. - -config CUSTOM_PATCH_ONLY - bool - prompt "Only use custom patches" - default n - depends on CUSTOM_PATCH - help - Don't apply patches coming with crosstool-NG, only those patches available - in the directory below. - - If you say 'N' here, then the patches provided with crosstool-NG will be - applied first, and then your patches. - -config CUSTOM_PATCH_DIR - string - prompt "Custom patch directory" - default "" - depends on CUSTOM_PATCH - help - Enter the custom patch directory here. - -config REMOVE_DOCS - bool - prompt "Remove documentation" - default n - help - Remove the installed documentation (man and info pages). - Gains around 8MiB for a uClibc-based, C and C++ compiler. - -config INSTALL_DIR_RO - bool - prompt "Render the toolchain read-only" - default n - help - Render the directory of the toolchain (and its sub-directories) - read-only. - - Usefull for toolchains destined for production. -- cgit v0.10.2-6-g49f6