ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-24 06:56:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
7c768b3ca1
crosstool-ng/config/global/build-behave.in

112 lines
3.3 KiB
Plaintext
Raw Normal View History

Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
# Options related to how the build behaves
comment "Build behavior"
config: hide more config options when a backend Hide the prompts for some behavioral options, for which the upper-layer build system is responsible for: - parallel jobs and maximum load - use pipes - use custom shell
2010-03-29 08:05:21 +00:00
comment "Build options hiden"
depends on BACKEND
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
config PARALLEL_JOBS
int
config: hide more config options when a backend Hide the prompts for some behavioral options, for which the upper-layer build system is responsible for: - parallel jobs and maximum load - use pipes - use custom shell
2010-03-29 08:05:21 +00:00
prompt "Number of parallel jobs" if ! BACKEND
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
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
config: hide more config options when a backend Hide the prompts for some behavioral options, for which the upper-layer build system is responsible for: - parallel jobs and maximum load - use pipes - use custom shell
2010-03-29 08:05:21 +00:00
prompt "Maximum allowed load" if ! BACKEND
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
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 USE_PIPES
bool
config: hide more config options when a backend Hide the prompts for some behavioral options, for which the upper-layer build system is responsible for: - parallel jobs and maximum load - use pipes - use custom shell
2010-03-29 08:05:21 +00:00
prompt "Use -pipe" if ! BACKEND
Break-down config/global.in into smaller, much more maintainable files. config/paths.in | 419 1 418 0 -------------------------------------------------------- 1 file changed, 1 insertion(+), 418 deletions(-)
2008-04-17 20:02:07 +00:00
default y
help
Use gcc's option -pipe to use pipes rather than temp files when building
the toolchain.
Allow using ash as the shell for ./configure and make. After an idea by "Martin Guy" <martinwguy@yahoo.it>: http://sourceware.org/ml/crossgcc/2008-08/msg00037.html /trunk/scripts/crosstool.sh | 4 4 0 0 ++++ /trunk/config/global/build-behave.in | 14 14 0 0 ++++++++++++++ 2 files changed, 18 insertions(+)
2008-08-25 19:44:39 +00:00
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
choice
bool
prompt "Shell to use as CONFIG_SHELL"
config: make CONFIG_SHELL default to bash Some components (eg. GMP) will fail to correctly build if the CONFIG_SHELL is not bash (eg. ash or dash). So make bash the default CONFIG_SHELL. Keep ash as a possible selection, as future versions of those currently /broken/ tools may come fixed wrt to CONFIG_SHELL being POSIX-ly compliant.
2009-08-06 17:40:26 +00:00
default CONFIG_SHELL_BASH
config: hide more config options when a backend Hide the prompts for some behavioral options, for which the upper-layer build system is responsible for: - parallel jobs and maximum load - use pipes - use custom shell
2010-03-29 08:05:21 +00:00
depends on ! BACKEND
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
config CONFIG_SHELL_SH
Allow using ash as the shell for ./configure and make. After an idea by "Martin Guy" <martinwguy@yahoo.it>: http://sourceware.org/ml/crossgcc/2008-08/msg00037.html /trunk/scripts/crosstool.sh | 4 4 0 0 ++++ /trunk/config/global/build-behave.in | 14 14 0 0 ++++++++++++++ 2 files changed, 18 insertions(+)
2008-08-25 19:44:39 +00:00
bool
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
prompt "sh (the system shell)"
Allow using ash as the shell for ./configure and make. After an idea by "Martin Guy" <martinwguy@yahoo.it>: http://sourceware.org/ml/crossgcc/2008-08/msg00037.html /trunk/scripts/crosstool.sh | 4 4 0 0 ++++ /trunk/config/global/build-behave.in | 14 14 0 0 ++++++++++++++ 2 files changed, 18 insertions(+)
2008-08-25 19:44:39 +00:00
help
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
Use 'sh' as CONFIG_SHELL.
Allow using ash as the shell for ./configure and make. After an idea by "Martin Guy" <martinwguy@yahoo.it>: http://sourceware.org/ml/crossgcc/2008-08/msg00037.html /trunk/scripts/crosstool.sh | 4 4 0 0 ++++ /trunk/config/global/build-behave.in | 14 14 0 0 ++++++++++++++ 2 files changed, 18 insertions(+)
2008-08-25 19:44:39 +00:00
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
./configure scripts and Makefiles make intensive use of calling
sub-shells. This is usually done by calling /bin/sh. /bin/sh ought
to be an at-least-POSIX-conformant shell (that is, able to interpret
POSIX shell scripts).
Allow using ash as the shell for ./configure and make. After an idea by "Martin Guy" <martinwguy@yahoo.it>: http://sourceware.org/ml/crossgcc/2008-08/msg00037.html /trunk/scripts/crosstool.sh | 4 4 0 0 ++++ /trunk/config/global/build-behave.in | 14 14 0 0 ++++++++++++++ 2 files changed, 18 insertions(+)
2008-08-25 19:44:39 +00:00
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
On many (most?) systems, /bin/sh is a symlink to bash. On some other
systems (eg. Ubuntu, latest Debian), /bin/sh points to dash (or ash).
bash is a full-featured shell, with many extension to POSIX, but is
quite slow (see ection BUGS in the bash man page), while dash is
faster, with very few extensions to POSIX. On the other hand, some
./configure scripts, although written to use /bin/sh, may really
require to be run by bash.
config: make CONFIG_SHELL default to bash Some components (eg. GMP) will fail to correctly build if the CONFIG_SHELL is not bash (eg. ash or dash). So make bash the default CONFIG_SHELL. Keep ash as a possible selection, as future versions of those currently /broken/ tools may come fixed wrt to CONFIG_SHELL being POSIX-ly compliant.
2009-08-06 17:40:26 +00:00
The default is to use bash, as some components (eg. GMP) will fail
to build with anything else than bash.
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
config CONFIG_SHELL_ASH
bool
[config] Warn againt using ash as CONFIG_SHELL It apears that more and more ./configure scripts and Makefiles make use of non-POSIXly correct shell constructs, that don't work with ash. For now, just warn the user against using ash, but keep it as an option in case newer versions of the /broken/ components come fixed, and we can again use ash, as it is in some cases really faster than bash.
2009-08-02 21:50:22 +00:00
prompt "ash (READ HELP!)"
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
help
Use 'ash' as CONFIG_SHELL.
See help for CONFIG_SHELL_SH, above, for more explanations.
[config] Warn againt using ash as CONFIG_SHELL It apears that more and more ./configure scripts and Makefiles make use of non-POSIXly correct shell constructs, that don't work with ash. For now, just warn the user against using ash, but keep it as an option in case newer versions of the /broken/ components come fixed, and we can again use ash, as it is in some cases really faster than bash.
2009-08-02 21:50:22 +00:00
NOTE: It is advised that you do NOT use ash as CONFIG_SHELL, as some
components are broken. If you decide to use ash, and the build breaks,
don't come moaning and set the CONFIG_SHELL to bash, below.
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
[config] Add bash as a possible CONFIG_SHELL On some systems and/or for some components, it may be necessary to explicitly use bash as the shell used by ./configure and Makefiles.
2009-08-02 18:06:06 +00:00
config CONFIG_SHELL_BASH
bool
prompt "bash"
help
Use 'bash' as CONFIG_SHELL.
See help for CONFIG_SHELL_SH, above, for more explanations.
[config] Allow user to specify custom CONFIG_SHELL In case the shell the user wants to use as CONFIG_SHELL is located in a weird place (eg. /opt/bash/bin/bash), or is weirdly named (eg. bash-4), let the user enter the patch to the shell.
2009-08-02 18:06:44 +00:00
config CONFIG_SHELL_CUSTOM
bool
prompt "custom shell"
help
Enter full path to the custom shell below.
See help for CONFIG_SHELL_SH, above, for more explanations.
[config] Change the way to select the CONFIG_SHELL Transform the single boolean option to a 'choice' selection with two options: "sh" and "ash". This is needed to later add "bash" as override.
2009-08-02 21:43:15 +00:00
endchoice
config CONFIG_SHELL
string
[config] Allow user to specify custom CONFIG_SHELL In case the shell the user wants to use as CONFIG_SHELL is located in a weird place (eg. /opt/bash/bin/bash), or is weirdly named (eg. bash-4), let the user enter the patch to the shell.
2009-08-02 18:06:44 +00:00
default "sh" if CONFIG_SHELL_SH
default "ash" if CONFIG_SHELL_ASH
default "bash" if CONFIG_SHELL_BASH
config: hide more config options when a backend Hide the prompts for some behavioral options, for which the upper-layer build system is responsible for: - parallel jobs and maximum load - use pipes - use custom shell
2010-03-29 08:05:21 +00:00
default "custom" if CONFIG_SHELL_CUSTOM || BACKEND
config CONFIG_SHELL_CUSTOM_PATH
string
prompt "Path to custom shell" if ! BACKEND
depends on CONFIG_SHELL_CUSTOM || BACKEND
default "/bin/sh"
Reference in New Issue Copy Permalink