1.1 --- a/docs/overview.txt Mon Jul 30 19:35:39 2007 +0000
1.2 +++ b/docs/overview.txt Thu Aug 30 19:49:21 2007 +0000
1.3 @@ -164,7 +164,7 @@
1.4 that you can use:
1.5
1.6 CT_TARGET:
1.7 - It represents the target triplet you are building for. You can use it for
1.8 + It represents the target tuple you are building for. You can use it for
1.9 example in the installation/prefix directory, such as:
1.10 /opt/x-tools/${CT_TARGET}
1.11
1.12 @@ -190,13 +190,13 @@
1.13
1.14 CT_PREFIX_DIR:
1.15 This is where the toolchain will be installed in (and for now, where it
1.16 - will run from). Common use it to add the target triplet in the directory
1.17 + will run from). Common use it to add the target tuple in the directory
1.18 path, such as (see above):
1.19 /opt/x-tools/${CT_TARGET}
1.20
1.21 CT_TARGET_VENDOR:
1.22 An identifier for your toolchain, will take place in the vendor part of the
1.23 - target triplet. It shall *not* contain spaces or dashes. Usually, keep it
1.24 + target tuple. It shall *not* contain spaces or dashes. Usually, keep it
1.25 to a one-word string, or use underscores to separate words if you need.
1.26 Avoid dots, commas, and special characters.
1.27
1.28 @@ -297,6 +297,21 @@
1.29 You can test-build all samples; simply call:
1.30 ct-ng regtest
1.31
1.32 +
1.33 +Overriding the number of // jobs |
1.34 +---------------------------------*
1.35 +
1.36 +If you want to override the number of jobs to run in // (the -j option to
1.37 +make), you can either re-enter the menuconfig, or simply add it on the command
1.38 +line, as such:
1.39 + ct-ng build.4
1.40 +
1.41 +which tells crosstool-NG to override the number of // jobs to 4.
1.42 +
1.43 +You can see the actions that support overriding the number of // jobs in
1.44 +the help menu. Those are the ones with [.#] after them (eg. build[.#] or
1.45 +regtest[.#], and so on...).
1.46 +
1.47 _______________________
1.48 /
1.49 Using the toolchain /
1.50 @@ -306,19 +321,19 @@
1.51 your PATH, such as:
1.52 export PATH="${PATH}:/your/toolchain/path/bin"
1.53
1.54 -and then using the target triplet to tell the build systems to use your
1.55 +and then using the target tuple to tell the build systems to use your
1.56 toolchain:
1.57 - ./configure --target=your-target-triplet
1.58 + ./configure --target=your-target-tuple
1.59 or
1.60 - make CC=your-target-triplet-gcc
1.61 + make CC=your-target-tuple-gcc
1.62 or
1.63 - make CROSS_COMPILE=your-target-triplet-
1.64 + make CROSS_COMPILE=your-target-tuple-
1.65 and so on...
1.66
1.67 When your root directory is ready, it is still missing some important bits: the
1.68 toolchain's libraries. To populate your root directory with those libs, just
1.69 run:
1.70 - your-target-triplet-populate -s /your/root -d /your/root-populated
1.71 + your-target-tuple-populate -s /your/root -d /your/root-populated
1.72
1.73 This will copy /your/root into /your/root-populated, and put the needed and only
1.74 the needed libraries there. Thus you don't polute /your/root with any cruft that