ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-29 09:08:52 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
aa6d4befd0
crosstool-ng/config/global/build-behave.in

154 lines
4.5 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 PARALLEL_JOBS
int
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
prompt "Number of parallel jobs"
config: use '0' for automatic number of jobs Also, make it the default. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-10-16 11:26:26 +00:00
default 0
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
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.
config: use '0' for automatic number of jobs Also, make it the default. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-10-16 11:26:26 +00:00
Enter 1 to have only one job at a time.
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: use '0' for automatic number of jobs Also, make it the default. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-10-16 11:26:26 +00:00
Enter 0 to set automatically based on how many processors the host has.
config: add a 'auto' value for the number of parallel jobs When CT_PARALLEL_JOBS is -1, set the number of parallel jobs to the number of online CPUs + 1. Update documentation to match. I find this useful when building in the cloud. You can use the same .config file and have the build adapt to the number of processors available. Limited testing shows that NCPUS+1 is faster than NCPUS+0 or NCPUS+2. Signed-off-by: Michael Hope <michael.hope@linaro.org>
2011-09-28 23:40:42 +00:00
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 LOAD
script: allow to pass any float value for CT_LOAD Signed-off-by: Samuel Martin <s.martin49@gmail.com> Message-Id: <b51acf21c72b4a8e882e.1359320015@laptop> Patchwork-Id: 216062
2013-01-27 16:54:19 +00:00
string
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
prompt "Maximum allowed load"
script: allow to pass any float value for CT_LOAD Signed-off-by: Samuel Martin <s.martin49@gmail.com> Message-Id: <b51acf21c72b4a8e882e.1359320015@laptop> Patchwork-Id: 216062
2013-01-27 16:54:19 +00:00
default ""
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
help
Specifies that no new jobs should be started if there are others jobs
running and the load average is at least this value.
script: allow to pass any float value for CT_LOAD Signed-off-by: Samuel Martin <s.martin49@gmail.com> Message-Id: <b51acf21c72b4a8e882e.1359320015@laptop> Patchwork-Id: 216062
2013-01-27 16:54:19 +00:00
Leave to empty for no load limit.
Note: any float value is allowed and will be passed to the '-l' option
of make (for further details, refer to the make manpage).
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 USE_PIPES
bool
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
prompt "Use -pipe"
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
scripts: add BUILD/HOST extra cflags/ldflags On some hosts, and for certain toolchains (eg. toolchain targetting the upcoming Darwin), it may be necessary to pass arbitrary CFLAGS and/or LDFLAGS when building the components. And necessary infrastructure: - EXTRA_{CFLAGS,LDFLAGS}_FOR_{BUILD,HOST} as config options - pass those extra flags to components Fix-up a slight typo in elf2flt at the same time (misnamed cflags). Signed-off-by: Yann Diorcet <diorcet.yann@gmail.com> Message-Id: <d24043276c9243a35421.1353077450@macbook-smorlat.local> Patchwork-Id: 199645
2012-11-16 14:25:57 +00:00
config EXTRA_CFLAGS_FOR_BUILD
string
prompt "Extra build compiler flags"
default ""
help
Extra flags to pass to the build C and C++ compiler.
May be used to change the default features of the build
compiler such as turning off the stack protector or fortify.
config EXTRA_LDFLAGS_FOR_BUILD
string
prompt "Extra build linker flags"
default ""
help
Extra flags to pass to the build linker.
May be used to change the default features of the build
linker.
config EXTRA_CFLAGS_FOR_HOST
scripts: support extra host compiler flags Allow the user to configure extra flags to pass to the host compiler at build time. Applies to both C and C++. Useful on Ubuntu to turn off the stack protector and fortify defaults so the program stands a better chance of running on other distros. Signed-off-by: Michael Hope <michael.hope@linaro.org> [yann.morin.1998@anciens.enib.fr: put the custom flags at the end] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-10-05 01:19:51 +00:00
string
prompt "Extra host compiler flags"
default ""
help
Extra flags to pass to the host C and C++ compiler.
May be used to change the default features of the host
compiler such as turning off the stack protector or fortify.
scripts: add BUILD/HOST extra cflags/ldflags On some hosts, and for certain toolchains (eg. toolchain targetting the upcoming Darwin), it may be necessary to pass arbitrary CFLAGS and/or LDFLAGS when building the components. And necessary infrastructure: - EXTRA_{CFLAGS,LDFLAGS}_FOR_{BUILD,HOST} as config options - pass those extra flags to components Fix-up a slight typo in elf2flt at the same time (misnamed cflags). Signed-off-by: Yann Diorcet <diorcet.yann@gmail.com> Message-Id: <d24043276c9243a35421.1353077450@macbook-smorlat.local> Patchwork-Id: 199645
2012-11-16 14:25:57 +00:00
config EXTRA_LDFLAGS_FOR_HOST
string
prompt "Extra host linker flags"
default ""
help
Extra flags to pass to the host linker.
May be used to change the default features of the host
linker.
scripts: support extra host compiler flags Allow the user to configure extra flags to pass to the host compiler at build time. Applies to both C and C++. Useful on Ubuntu to turn off the stack protector and fortify defaults so the program stands a better chance of running on other distros. Signed-off-by: Michael Hope <michael.hope@linaro.org> [yann.morin.1998@anciens.enib.fr: put the custom flags at the end] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-10-05 01:19:51 +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] 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: simplify setting CONFIG_SHELL, add a bit to the help entry Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-10-11 19:43:42 +00:00
Unless you have a very strong reason not to (eg. you are debugging
the bashisms in a ./configure script), you should use the default,
and use 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
[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: 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
config CONFIG_SHELL_CUSTOM_PATH
string
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
prompt "Path to custom shell"
depends on CONFIG_SHELL_CUSTOM
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 "/bin/sh"
config: simplify setting CONFIG_SHELL, add a bit to the help entry Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-10-11 19:43:42 +00:00
# Ditto.
# And we must use the ./configured bash...
config CONFIG_SHELL
string
default "/bin/sh" if CONFIG_SHELL_SH
default "/bin/ash" if CONFIG_SHELL_ASH
default "${bash}" if CONFIG_SHELL_BASH
Retire BACKEND stuff ... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-04-23 06:51:05 +00:00
default CONFIG_SHELL_CUSTOM_PATH if CONFIG_SHELL_CUSTOM
Reference in New Issue Copy Permalink