From 09f0dcc66fbec2f35682d1362f73704d5708ae33 Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN\"" Date: Wed, 15 Aug 2007 16:18:35 +0000 Subject: Change "triplet" (target triplet) to "tuple". That sounds better! Document overriding the number of // jobs. Some small documentation fixes. diff --git a/config/toolchain.in b/config/toolchain.in index 6eb3539..bebf5b8 100644 --- a/config/toolchain.in +++ b/config/toolchain.in @@ -74,9 +74,9 @@ config TARGET_VENDOR prompt "Vendor string" default "unknown" help - Vendor part of the machine triplet. + Vendor part of the target tuple. - A triplet is of the form arch-vendor-kernel-system. + A tuple is of the form arch-vendor-kernel-system. You can set the second part, vendor, to whatever you see fit. Use a single word, or use underscores "_" to separate words. @@ -88,7 +88,7 @@ config TARGET_ALIAS_SED_EXPR default "" help Normaly, you'd call your toolchain components (especially gcc) by - prefixing the target triplet followed by a dash and the component name + prefixing the target tuple followed by a dash and the component name (eg. armeb-unknown-linux-uclibc-gcc). You can enter here a sed expression to be applied to ${CT_TARGET} to @@ -107,7 +107,7 @@ config TARGET_ALIAS default "" help Normaly, you'd call your toolchain components (especially gcc) by - prefixing the target triplet followed by a dash and the component name + prefixing the target tuple followed by a dash and the component name (eg. armeb-unknown-linux-uclibc-gcc). You can enter a shortcut here. This string will be used to create @@ -167,7 +167,7 @@ config TOOLCHAIN_TYPE config BUILD string - prompt "Build system triplet" + prompt "Build system tuple" default "" help Canonical name of the machine building the toolchain. @@ -187,7 +187,7 @@ config CC_NATIVE config HOST string - prompt "Host system triplet" + prompt "Host system tuple" default "" depends on NATIVE || CANADIAN help diff --git a/docs/ct-ng.1.in b/docs/ct-ng.1.in index b24b22a..49dbdca 100644 --- a/docs/ct-ng.1.in +++ b/docs/ct-ng.1.in @@ -49,7 +49,7 @@ file, and ask for newer options if there are any. Save the current .B crosstool-NG configuration, and associated components' config files, into a sample. Samples -are saved in their own sub-directory, named after the target's triplet, in the +are saved in their own sub-directory, named after the target's tuple, in the .I samples sub-directory of the current directory. If that was not clear: @@ -57,7 +57,7 @@ If that was not clear: Samples can be later recalled by calling .B ct-ng -with the target triplet they represent. +with the target tuple they represent. ." .TP .B build @@ -149,7 +149,7 @@ entire important directories could be removed (eg. .IR /usr ), although .B crosstool-NG -will refuse to install in some well known critical directories. +will refuse to install toolchains in some well known critical directories. ." .SH AUTHORS .MTO "yann.morin.1998@anciens.enib.fr" "Yann E. MORIN" "" diff --git a/docs/overview.txt b/docs/overview.txt index 527d854..52e73f3 100644 --- a/docs/overview.txt +++ b/docs/overview.txt @@ -164,7 +164,7 @@ There are three environment variables that are computed by crosstool-NG, and that you can use: CT_TARGET: - It represents the target triplet you are building for. You can use it for + It represents the target tuple you are building for. You can use it for example in the installation/prefix directory, such as: /opt/x-tools/${CT_TARGET} @@ -190,13 +190,13 @@ CT_LOCAL_TARBALLS_DIR: CT_PREFIX_DIR: This is where the toolchain will be installed in (and for now, where it - will run from). Common use it to add the target triplet in the directory + will run from). Common use it to add the target tuple in the directory path, such as (see above): /opt/x-tools/${CT_TARGET} CT_TARGET_VENDOR: An identifier for your toolchain, will take place in the vendor part of the - target triplet. It shall *not* contain spaces or dashes. Usually, keep it + target tuple. It shall *not* contain spaces or dashes. Usually, keep it to a one-word string, or use underscores to separate words if you need. Avoid dots, commas, and special characters. @@ -297,6 +297,21 @@ Testing all toolchains at once | You can test-build all samples; simply call: ct-ng regtest + +Overriding the number of // jobs | +---------------------------------* + +If you want to override the number of jobs to run in // (the -j option to +make), you can either re-enter the menuconfig, or simply add it on the command +line, as such: + ct-ng build.4 + +which tells crosstool-NG to override the number of // jobs to 4. + +You can see the actions that support overriding the number of // jobs in +the help menu. Those are the ones with [.#] after them (eg. build[.#] or +regtest[.#], and so on...). + _______________________ / Using the toolchain / @@ -306,19 +321,19 @@ Using the toolchain is as simple as adding the toolchain's bin directory in your PATH, such as: export PATH="${PATH}:/your/toolchain/path/bin" -and then using the target triplet to tell the build systems to use your +and then using the target tuple to tell the build systems to use your toolchain: - ./configure --target=your-target-triplet + ./configure --target=your-target-tuple or - make CC=your-target-triplet-gcc + make CC=your-target-tuple-gcc or - make CROSS_COMPILE=your-target-triplet- + make CROSS_COMPILE=your-target-tuple- and so on... When your root directory is ready, it is still missing some important bits: the toolchain's libraries. To populate your root directory with those libs, just run: - your-target-triplet-populate -s /your/root -d /your/root-populated + your-target-tuple-populate -s /your/root -d /your/root-populated This will copy /your/root into /your/root-populated, and put the needed and only the needed libraries there. Thus you don't polute /your/root with any cruft that diff --git a/scripts/crosstool.sh b/scripts/crosstool.sh index 5802266..a0895f3 100755 --- a/scripts/crosstool.sh +++ b/scripts/crosstool.sh @@ -72,8 +72,8 @@ CT_HasOrAbort lynx CT_DoLog INFO "Building environment variables" -# Target triplet: CT_TARGET needs a little love: -CT_DoBuildTargetTriplet +# Target tuple: CT_TARGET needs a little love: +CT_DoBuildTargetTuple # Kludge: If any of the configured options needs CT_TARGET, # then rescan the options file now: diff --git a/scripts/functions b/scripts/functions index eade487..67ac834 100644 --- a/scripts/functions +++ b/scripts/functions @@ -480,12 +480,12 @@ CT_DoConfigSub() { fi } -# Compute the target triplet from what is provided by the user -# Usage: CT_DoBuildTargetTriplet +# Compute the target tuple from what is provided by the user +# Usage: CT_DoBuildTargetTuple # In fact this function takes the environment variables to build the target -# triplet. It is needed both by the normal build sequence, as well as the +# tuple. It is needed both by the normal build sequence, as well as the # sample saving sequence. -CT_DoBuildTargetTriplet() { +CT_DoBuildTargetTuple() { case "${CT_ARCH_BE},${CT_ARCH_LE}" in y,) target_endian_eb=eb; target_endian_el=;; ,y) target_endian_eb=; target_endian_el=el;; diff --git a/scripts/saveSample.sh b/scripts/saveSample.sh index 4aee0eb..9a3d8fb 100755 --- a/scripts/saveSample.sh +++ b/scripts/saveSample.sh @@ -18,8 +18,8 @@ rm -f "${tmp_log_file}" CT_TestOrAbort "Configuration file not found. Please create one." -f "${CT_TOP_DIR}/.config" . "${CT_TOP_DIR}/.config" -# Target triplet: CT_TARGET needs a little love: -CT_DoBuildTargetTriplet +# Target tuple: CT_TARGET needs a little love: +CT_DoBuildTargetTuple # Kludge: if any of the config options needs either CT_TARGET or CT_TOP_DIR, # re-parse them: diff --git a/scripts/tarball.sh.broken b/scripts/tarball.sh.broken index e94ac6e..63d27cd 100755 --- a/scripts/tarball.sh.broken +++ b/scripts/tarball.sh.broken @@ -16,7 +16,7 @@ rm -f "${tmp_log_file}" # Parse the configuration file: . ${CT_TOP_DIR}/.config -CT_DoBuildTargetTriplet +CT_DoBuildTargetTuple # Kludge: if any of the config options needs either CT_TARGET or CT_TOP_DIR, # re-parse them: -- cgit v0.10.2-6-g49f6