path: root/config/global/
AgeCommit message (Collapse)AuthorFilesLines
2017-01-20Make build-all rely on kconfig options.Alexey Neyman1-1/+5
For that, make CT_BUILD_TOP_DIR a non-settable config option (so that it is recursively expanded with CT_HOST/CT_TARGET). Use a common prefix, with same default as for regular sample build. Use to determine host toolchain path (for canadian crosses) and build directory to be removed. Remove LIBC_SYSROOT_ARG (unused). Signed-off-by: Alexey Neyman <>
2017-01-20Simplify config saving.Alexey Neyman1-2/+2
Instead of hardcoding defaults in, have the same defaults in config. Then we can just remove them when saving the config.
2017-01-20Install canadian crosses into a separate subdir.Alexey Neyman1-1/+1
Makes them sorted out by host, and removes the need for similar hack in Change how canadian crosses are named: using `=' character resulted in Glibc build failure. Move loading config into a common function, CT_LoadConfig. Signed-off-by: Alexey Neyman <>
2016-12-19Kill CT_INSTALL_DIR.Alexey Neyman1-14/+1
We now use CT_PREFIX and expect the resulting toolchain to be relocatable. Signed-off-by: Alexey Neyman <>
2015-12-08config: Remove CUSTOM_LOCATION_ROOT_DIRBryan Hundven1-9/+0
On top of making <component>_CUSTOM much more complicated to rewrite, you couldn't depend on a requirement for all of the components to treat custom sources the same with it around. If you need a custom source for a component, define it in the component. Signed-off-by: Bryan Hundven <> Reviewed-by: "Yann E. MORIN" <>
2015-11-30gcc: Remove gcc <= 4.7.xBryan Hundven1-1/+0
As per #222, in crosstool-NG >= 1.23.0, we will only support: [upstream supported gcc versions] - 1 As of this writing, these versions are: * 5.2.0 * 4.9.3 * 4.8.5 (the -1, since development on 4.8.x is now closed) I plan to keep 4.8.5 around because of some architectures having issues with over-optimization or just faulty optimization in the 4.9.x and possibly newer versions. I also cleaned up a requirement for glibc to depend on >= gcc-4.6.x for >= glibc-2.20, but since the lowest gcc we support after this change is >= 4.8.5, this condition can go away. Patches for older gcc versions are removed in the next commit. This closes #222 Signed-off-by: Bryan Hundven <>
2015-11-11Use install-strip target for gcc optionallyIlya Lyubimov1-3/+13
2012-12-26all: unmark experimental featuresYann E. MORIN"1-1/+1
It's been some time now we've had those features, so unmark them being experimental. It does not mean everything is perfect, but may gather some more testing of those features. Signed-off-by: "Yann E. MORIN" <>
2012-10-04scripts/functions: add a generic custom location infrastructureDavid Holsgrove1-0/+9
Add a generic custom location infrastructure (inspired by the one in kernel/linux) to allow the user to use custom tarballs or directories for any component. Signed-off-by: "David Holsgrove" <> [ move config option, improve help text, fix API doc] Signed-off-by: "Yann E. MORIN" <> Message-Id: <131c163c69f9cc81d2be.1349931191@localhost.localdomain> PatchWork-Id: 190784 Message-Id: <0bbaba9190a76ba97f72.1349931192@localhost.localdomain> PatchWork-Id: 190785
2011-11-15scripts: add support for building manualsYann E. MORIN"1-0/+8
Add support for building the HTML and PDF manuals for the major components. Implement for binutils, GCC, GDB, and GLIBC. Always build all manuals and install a subset. Be explicit about the subset to reduce the clutter and to avoid getting copies of common manuals like bfd from all of the sourceware based components. Downside of being explicit is that you need to update it when a new component comes along. Build the manuals as part of the last GCC build, namely 'cc' for glibc based ones and cc_core_pass_2 for baremetal. An example of the output is at: Signed-off-by: Michael Hope <> [ depends on ! remove docs; gold manual install] Signed-off-by: "Yann E. MORIN" <>
2011-07-17misc: fix more typos here and there...Yann E. MORIN"1-3/+3
Reported-by: "Antony N. Pavlov" <> Signed-off-by: "Yann E. MORIN" <>
2011-05-31kconfig: remove useless 'default n'Benoît THÉBAUDEAU"1-1/+0
kconfig bools are disabled by default, so specifying 'default n' is useless and noisy. This patch removes all occurrences of 'default n'. Signed-off-by: "Benoît THÉBAUDEAU" <>
2011-04-27config: small help fix up for work dir defaultYann E. MORIN"1-1/+1
Signed-off-by: "Yann E. MORIN" <>
2011-01-28config: add an option not to remove the destination directoryYann E. MORIN"1-0/+22
In certain circumstances, removing the destination/installation directory is a bad idea. For example, when the build environment is already taking care of sanitising the build tree, and pre-installs stuff in there, it is a very bad idea to remove the destination directory. This happens now in buildroot, as the crostool-NG backend now installs the toolchain in the common host-tools directory, and pre-install there a few host-utilities (eg. host-automake and host-gawk). Provide a config knob to turn on/off the removal of the destination directory, defaulting to 'y' (previous behavior), and forced to 'n' when used as a backend. Reported-by: Peter Korsgaard <> Signed-off-by: "Yann E. MORIN" <>
2010-09-12config: change name of default build dirYann E. MORIN"1-1/+1
'targets' is not really meaningfull. 'build' means what it means. '.build' just hides it as well! :-) Signed-off-by: "Yann E. MORIN" <>
2010-05-27scripts: add option to strip all toolchain executablesRemy Bohmer1-0/+10
To reduce filesizes of the toolchain and even improve build times of projects to be build with this toolchain it is usefull to strip the delivered toolchain executables. Since it is not likely that we will debug the toolchain executables itself we do not need the debug information inside the executables itself. Signed-off-by: Remy Bohmer <>
2010-03-29config: hide paths when used as a backendYann E. MORIN"1-6/+7
When crosstool-NG is used as a backend, it is the responsibility of the upper-layer build-system to properly set paths, so we just hide the prompts in this case.
2009-08-31config: move the patch choice to the extract sectionYann E. MORIN"1-80/+0
Choosing the origin of the patches to apply is best done in the 'extract' section.
2009-08-31config: add fallback to patch orderYann E. MORIN"1-0/+22
Add the possibility to fallback to either bundled or local patches if local or bundled are missing.
2009-08-31config: add the local,bundled patch orderYann E. MORIN"1-0/+9
This ordering first applies the local patches, then the bundeld ones.
2009-08-31config: make selecting the patch origin a choice rather than a boolYann E. MORIN"1-20/+38
2008-08-01Change some config items' default values.Yann E. MORIN"1-2/+2
/trunk/config/global/ | 4 2 2 0 ++-- /trunk/config/global/ | 2 1 1 0 +- 2 files changed, 3 insertions(+), 3 deletions(-)
2008-06-25Change default path where toolchain will run from to ↵Yann E. MORIN"1-1/+1
"${HOME}/x-tools/${CT_TARGET}". /trunk/config/global/ | 2 1 1 0 +- 1 file changed, 1 insertion(+), 1 deletion(-)
2008-06-24Allow to store working files outside the build tree (eg. incase the working ↵Yann E. MORIN"1-1/+22
tree is on the network). /trunk/scripts/ | 9 5 4 0 +++++---- /trunk/config/global/ | 23 22 1 0 ++++++++++++++++++++++- 2 files changed, 27 insertions(+), 5 deletions(-)
2008-04-17Move config files around, and clean up the mess in the config/ directory.Yann E. MORIN"1-0/+89
config/kernel/ | 12 6 6 0 +- config/ | 89 0 89 0 ---------------- config/ | 168 0 168 0 ------------------------------ config/ | 2 1 1 0 config/ | 42 0 42 0 -------- config/ | 2 1 1 0 config/ | 110 0 110 0 -------------------- config/ | 45 0 45 0 -------- config/ | 101 0 101 0 ------------------ config/ | 62 0 62 0 ----------- config/ | 82 0 82 0 --------------- config/ | 134 0 134 0 ------------------------ config/ | 10 5 5 0 +- config/ | 171 0 171 0 ------------------------------- config/ | 130 0 130 0 ------------------------ config/ | 124 0 124 0 ---------------------- config/ | 4 2 2 0 17 files changed, 15 insertions(+), 1273 deletions(-)