summaryrefslogtreecommitdiff
path: root/docs/overview.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/overview.txt')
-rw-r--r--docs/overview.txt31
1 files changed, 23 insertions, 8 deletions
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