mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2025-02-20 17:12:55 +00:00
scripts/showSamples.sh:
- revert sample dumping to not show the components versions; docs/overview.txt: - reorder docs/overview.txt so that configuring comes before running, - tell about regtest; Makefile: config/global.in: - point to docs/overview.txt for the list of steps;
This commit is contained in:
Yann E. MORIN"
parent
b166f010a2
commit
ca5213a387
2
Makefile
2
Makefile
@ -37,7 +37,7 @@ help::
|
||||
@echo 'Distribution targets:'
|
||||
@echo ' tarball - Build a tarball of the configured toolchain'
|
||||
@echo ''
|
||||
@echo 'Environement variables:'
|
||||
@echo 'Environement variables (see docs/overview.txt):'
|
||||
@echo ' STOP - Stop the build just after this step'
|
||||
@echo ' RESTART - Restart the build just before this step'
|
||||
@echo ''
|
||||
|
||||
@ -58,22 +58,12 @@ config DEBUG_CT_SAVE_STEPS
|
||||
default n
|
||||
help
|
||||
If you say 'y' here, then you will be able to restart crosstool-NG at
|
||||
any step by typing:
|
||||
make RESTART=<step_nane>
|
||||
|
||||
where step_name is one of:
|
||||
- kernel_hdr
|
||||
- binutils
|
||||
- libc_hdr
|
||||
- cc_core
|
||||
- libfloat
|
||||
- libc
|
||||
- cc
|
||||
- libc_fin
|
||||
- debug
|
||||
any step.
|
||||
|
||||
It is not currently possible to rstart at any of the debug facility.
|
||||
They are treated a s a whole.
|
||||
They are treated as a whole.
|
||||
|
||||
See docs/overview.txt for the list of steps.
|
||||
|
||||
config DEBUG_CT_SAVE_STEPS_GZIP
|
||||
bool
|
||||
|
||||
@ -84,71 +84,6 @@ this way, and name the new implementation ct-ng, standing for crosstool Next
|
||||
Generation, as many other comunity projects do, and as a wink at the TV series
|
||||
"Star Trek: The Next Generation". ;-)
|
||||
|
||||
_____________
|
||||
/
|
||||
Operation /
|
||||
__________/
|
||||
|
||||
ct-ng is configured by a configurator presenting a menu-stuctured set of
|
||||
options. These options let you specify the way you want your toolchain built,
|
||||
where you want it installed, what architecture and specific processor it
|
||||
will support, the version of the components you want to use, etc... The
|
||||
value for those options are then stored in a configuration file.
|
||||
|
||||
To enter the menu, type:
|
||||
make menuconfig
|
||||
|
||||
To build the so-configured target, simply type:
|
||||
make
|
||||
|
||||
This will use the above configuration to retrieve, extract and patch the
|
||||
components, build, install and eventually test your newly built toolchain.
|
||||
|
||||
You are then free to add the toolchain /bin directory in your PATH to use
|
||||
it at will.
|
||||
|
||||
In any case, you can get some terse help. Just type:
|
||||
make help
|
||||
|
||||
|
||||
Stoping and restarting a build |
|
||||
-------------------------------*
|
||||
|
||||
If you want to stop the build after a step you are debugging, you can pass the
|
||||
variable STOP to make:
|
||||
make STOP=some_step
|
||||
|
||||
Conversely, if you want to restart a build at a specific step you are
|
||||
debugging, you can pass the RESTART variable to make:
|
||||
make RESTART=some_step
|
||||
|
||||
The list of steps is, in order of appearence in the build process:
|
||||
- libc_check_config
|
||||
- kernel_check_config
|
||||
- kernel_headers
|
||||
- binutils
|
||||
- cc_core_pass_1
|
||||
- libc_headers
|
||||
- libc_start_files
|
||||
- cc_core_pass_2
|
||||
- libfloat
|
||||
- libc
|
||||
- cc
|
||||
- libc_finish
|
||||
- tools
|
||||
- debug
|
||||
|
||||
Alternatively, you can call make with the name of a step to just do that step:
|
||||
make libc_headers
|
||||
is equivalent to:
|
||||
make RESTART=libs_headers STOP=libc_headers
|
||||
|
||||
The shortcuts -step_name and step_name- allow to respectively stop or restart
|
||||
at that step. Thus:
|
||||
make -libc_headers and: make libc_headers-
|
||||
are equivalent to:
|
||||
make STOP=libc_headers and: make RESTART=libc_headers
|
||||
|
||||
____________________________
|
||||
/
|
||||
Configuring crosstool-NG /
|
||||
@ -157,6 +92,9 @@ _________________________/
|
||||
crosstool-NG is configured the same way you configure your Linux kernel: by
|
||||
using a curses-based menu. It is assumed you now how to handle this.
|
||||
|
||||
To enter the menu, type:
|
||||
make menuconfig
|
||||
|
||||
Almost every config item has a help entry. Read it carefully.
|
||||
|
||||
String and number options can refer to environment variables. In such a case,
|
||||
@ -209,6 +147,79 @@ CT_TARGET_ALIAS:
|
||||
An alias for the toolchian. It will be used as a prefix to the toolchain
|
||||
tools. For example, you will have ${CT_TARGET_ALIAS}-gcc
|
||||
|
||||
________________________
|
||||
/
|
||||
Running crosstool-NG /
|
||||
_____________________/
|
||||
|
||||
ct-ng is configured by a configurator presenting a menu-stuctured set of
|
||||
options. These options let you specify the way you want your toolchain built,
|
||||
where you want it installed, what architecture and specific processor it
|
||||
will support, the version of the components you want to use, etc... The
|
||||
value for those options are then stored in a configuration file.
|
||||
|
||||
To build the toolchain, simply type:
|
||||
make
|
||||
|
||||
This will use the above configuration to retrieve, extract and patch the
|
||||
components, build, install and eventually test your newly built toolchain.
|
||||
|
||||
You are then free to add the toolchain /bin directory in your PATH to use
|
||||
it at will.
|
||||
|
||||
In any case, you can get some terse help. Just type:
|
||||
make help
|
||||
|
||||
|
||||
Stoping and restarting a build |
|
||||
-------------------------------*
|
||||
|
||||
If you want to stop the build after a step you are debugging, you can pass the
|
||||
variable STOP to make:
|
||||
make STOP=some_step
|
||||
|
||||
Conversely, if you want to restart a build at a specific step you are
|
||||
debugging, you can pass the RESTART variable to make:
|
||||
make RESTART=some_step
|
||||
|
||||
The list of steps is, in order of appearence in the build process:
|
||||
- libc_check_config
|
||||
- kernel_check_config
|
||||
- kernel_headers
|
||||
- binutils
|
||||
- cc_core_pass_1
|
||||
- libc_headers
|
||||
- libc_start_files
|
||||
- cc_core_pass_2
|
||||
- libfloat
|
||||
- libc
|
||||
- cc
|
||||
- libc_finish
|
||||
- tools
|
||||
- debug
|
||||
|
||||
Alternatively, you can call make with the name of a step to just do that step:
|
||||
make libc_headers
|
||||
is equivalent to:
|
||||
make RESTART=libs_headers STOP=libc_headers
|
||||
|
||||
The shortcuts -step_name and step_name- allow to respectively stop or restart
|
||||
at that step. Thus:
|
||||
make -libc_headers and: make libc_headers-
|
||||
are equivalent to:
|
||||
make STOP=libc_headers and: make RESTART=libc_headers
|
||||
|
||||
Note that in order to restart a build, you'll have to say 'Y' to the config
|
||||
option CT_DEBUG_CT_SAVE_STEPS, and that the previous build effectively went
|
||||
that far.
|
||||
|
||||
|
||||
Testing all toolchains at once |
|
||||
-------------------------------*
|
||||
|
||||
You can test-build all samples; simply call:
|
||||
make regtest
|
||||
|
||||
___________________
|
||||
/
|
||||
Toolchain types /
|
||||
|
||||
@ -10,12 +10,9 @@ export GREP_OPTIONS=
|
||||
dump_single_sample() {
|
||||
local width="$1"
|
||||
local sample="$2"
|
||||
. "${CT_TOP_DIR}/samples/${sample}/crosstool.config"
|
||||
printf " %-*s" ${width} "${sample}"
|
||||
[ -f "${CT_TOP_DIR}/samples/${sample}/broken" ] && printf " (broken)"
|
||||
echo
|
||||
echo " \ ${CT_KERNEL}-${CT_KERNEL_VERSION} binutils-${CT_BINUTILS_VERSION}"
|
||||
echo " \_ ${CT_CC}-${CT_CC_VERSION} ${CT_LIBC}-${CT_LIBC_VERSION}"
|
||||
}
|
||||
|
||||
# Get largest sample width
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user