Move snapshots version after numbered versions (aka releases).
/trunk/config/debug/gdb.in | 13 7 6 0 +++++++------
/trunk/config/libc/glibc.in | 21 11 10 0 +++++++++++----------
/trunk/config/libc/uClibc.in | 21 11 10 0 +++++++++++----------
/trunk/config/libc/eglibc.in | 13 7 6 0 +++++++------
4 files changed, 36 insertions(+), 32 deletions(-)
1 File.........: overview.txt
2 Content......: Overview of how crosstool-NG works.
3 Copyrigth....: (C) 2007 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
4 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
14 Installing crosstool-NG
19 Configuring crosstool-NG
20 Interesting config options
21 Re-building an existing toolchain
23 Stopping and restarting a build
24 Testing all toolchains at once
25 Overriding the number of // jobs
32 Adding a new version of a component
40 crosstool-NG aims at building toolchains. Toolchains are an essential component
41 in a software development project. It will compile, assemble and link the code
42 that is being developed. Some pieces of the toolchain will eventually end up
43 in the resulting binary/ies: static libraries are but an example.
45 So, a toolchain is a very sensitive piece of software, as any bug in one of the
46 components, or a poorly configured component, can lead to execution problems,
47 ranging from poor performance, to applications ending unexpectedly, to
48 mis-behaving software (which more than often is hard to detect), to hardware
49 damage, or even to human risks (which is more than regrettable).
51 Toolchains are made of different piece of software, each being quite complex
52 and requiring specially crafted options to build and work seamlessly. This
53 is usually not that easy, even in the not-so-trivial case of native toolchains.
54 The work reaches a higher degree of complexity when it comes to cross-
55 compilation, where it can become quite a nightmare...
57 Some cross-toolchains exist on the internet, and can be used for general
58 development, but they have a number of limitations:
59 - they can be general purpose, in that they are configured for the majority:
60 no optimisation for your specific target,
61 - they can be prepared for a specific target and thus are not easy to use,
62 nor optimised for, or even supporting your target,
63 - they often are using aging components (compiler, C library, etc...) not
64 supporting special features of your shiny new processor;
65 On the other side, these toolchain offer some advantages:
66 - they are ready to use and quite easy to install and setup,
67 - they are proven if used by a wide community.
69 But once you want to get all the juice out of your specific hardware, you will
70 want to build your own toolchain. This is where crosstool-NG comes into play.
72 There are also a number of tools that build toolchains for specific needs,
73 which are not really scalable. Examples are:
74 - buildroot (buildroot.uclibc.org) whose main purpose is to build root file
75 systems, hence the name. But once you have your toolchain with buildroot,
76 part of it is installed in the root-to-be, so if you want to build a whole
77 new root, you either have to save the existing one as a template and
78 restore it later, or restart again from scratch. This is not convenient,
79 - ptxdist (www.pengutronix.de/software/ptxdist), whose purpose is very
81 - other projects (openembedded.org for example), which are again used to
82 build root file systems.
84 crosstool-NG is really targeted at building toolchains, and only toolchains.
85 It is then up to you to use it the way you want.
92 crosstool was first 'conceived' by Dan Kegel, who offered it to the community
93 as a set of scripts, a repository of patches, and some pre-configured, general
94 purpose setup files to be used to configure crosstool. This is available at
95 http://www.kegel.com/crosstool, and the subversion repository is hosted on
96 google at http://code.google.com/p/crosstool/.
98 I once managed to add support for uClibc-based toolchains, but it did not make
99 into mainline, mostly because I didn't have time to port the patch forward to
100 the new versions, due in part to the big effort it was taking.
102 So I decided to clean up crosstool in the state it was, re-order the things
103 in place, add appropriate support for what I needed, that is uClibc support
104 and a menu-driven configuration, named the new implementation crosstool-NG,
105 (standing for crosstool Next Generation, as many other comunity projects do,
106 and as a wink at the TV series "Star Trek: The Next Generation" ;-) ) and
107 made it available to the community, in case it was of interest to any one.
109 ___________________________
111 Installing crosstool-NG /
112 ________________________/
114 There are two ways you can use crosstool-NG:
115 - build and install it, then get rid of the sources like you'd do for most
117 - or only build it and run from the source directory.
119 The former should be used if you got crosstool-NG from a packaged tarball, see
120 "Install method", below, while the latter is most useful for developpers that
121 checked the code out from SVN, and want to submit patches, see "The Hacker's
127 If you go for the install, then you just follow the classical, but yet easy
129 ./configure --prefix=/some/place
132 export PATH="${PATH}:/some/place/bin"
134 You can then get rid of crosstool-NG source. Next create a directory to serve
135 as a working place, cd in there and run:
138 See below for complete usage.
143 If you go the hacker's way, then the usage is a bit different, although very
148 Now, *do not* remove crosstool-NG sources. They are needed to run crosstool-NG!
149 Stay in the directory holding the sources, and run:
152 See below for complete usage.
154 Now, provided you checked-out the code, you can send me your interesting changes
158 and mailing me the result! :-P
163 crosstool-NG comes with a shell script fragment that defines bash-compatible
164 completion. That shell fragment is currently not installed automatically, but
167 To install the shell script fragment, you have two options:
168 - install system-wide, most probably by copying ct-ng.comp into
169 /etc/bash_completion.d/
170 - install for a single user, by copying ct-ng.comp into ${HOME}/ and
171 sourcing this file from your ${HOME}/.bashrc
176 Some people contibuted code that couldn't get merged for various reasons. This
177 code is available as patches in the contrib/ sub-directory. These patches are
178 to be applied to the source of crosstool-NG, prior to installing.
180 An easy way to use contributed code is to pass the --with-contrib= option to
181 ./configure. The possible values depend upon which contributions are packaged
182 with your version, but you can get with it with passing one of those two
185 will list all available contributions
188 will select all avalaible contributions
190 There is no guarantee that a particuliar contribution applies to the current
191 version of crosstool-ng, or that it will work at all. Use contributions at
194 ____________________________
196 Configuring crosstool-NG /
197 _________________________/
199 crosstool-NG is configured with a configurator presenting a menu-stuctured set
200 of options. These options let you specify the way you want your toolchain
201 built, where you want it installed, what architecture and specific processor it
202 will support, the version of the components you want to use, etc... The
203 value for those options are then stored in a configuration file.
205 The configurator works the same way you configure your Linux kernel. It is
206 assumed you now how to handle this.
208 To enter the menu, type:
211 Almost every config item has a help entry. Read them carefully.
213 String and number options can refer to environment variables. In such a case,
214 you must use the shell syntax: ${VAR}. You shall neither single- nor double-
215 quote the string/number options.
217 There are three environment variables that are computed by crosstool-NG, and
221 It represents the target tuple you are building for. You can use it for
222 example in the installation/prefix directory, such as:
223 /opt/x-tools/${CT_TARGET}
226 The top directory where crosstool-NG is running. You shouldn't need it in
227 most cases. There is one case where you may need it: if you have local
228 patches and you store them in your running directory, you can refer to them
229 by using CT_TOP_DIR, such as:
230 ${CT_TOP_DIR}/patches.myproject
233 The version of crosstool-NG you are using. Not much use for you, but it's
234 there if you need it.
236 Interesting config options |
237 ---------------------------+
239 CT_LOCAL_TARBALLS_DIR:
240 If you already have some tarballs in a direcotry, enter it here. That will
241 speed up the retrieving phase, where crosstool-NG would otherwise download
245 This is where the toolchain will be installed in (and for now, where it
246 will run from). Common use is to add the target tuple in the directory
247 path, such as (see above):
248 /opt/x-tools/${CT_TARGET}
251 An identifier for your toolchain, will take place in the vendor part of the
252 target tuple. It shall *not* contain spaces or dashes. Usually, keep it
253 to a one-word string, or use underscores to separate words if you need.
254 Avoid dots, commas, and special characters.
257 An alias for the toolchian. It will be used as a prefix to the toolchain
258 tools. For example, you will have ${CT_TARGET_ALIAS}-gcc
260 Also, if you think you don't see enough versions, you can try to enable one of
264 Show obsolete versions or tools. Most of the time, you don't want to base
265 your toolchain on too old a version (of gcc, for example). But at times, it
266 can come handy to use such an old version for regression tests. Those old
267 versions are hidden behind CT_OBSOLETE.
270 Show experimental versions or tools. Again, you might not want to base your
271 toolchain on too recent tools (eg. gcc) for production. But if you need a
272 feature present only in a recent version, or a new tool, you can find them
273 hidden behind CT_EXPERIMENTAL.
276 Show broken versions or tools. Some usefull tools are currently broken: they
277 won't compile, run, or worse, cause defects when running. But if you are
278 brave enough, you can try and debug them. They are hidden behind CT_BROKEN,
279 which itself is hidden behind CT_EXPERIMENTAL.
281 Re-building an existing toolchain |
282 ----------------------------------+
284 If you have an existing toolchain, you can re-use the options used to build it
285 to create a new toolchain. That needs a very little bit of effort on your side
286 but is quite easy. The options to build a toolchain are saved in the build log
287 file that is saved within the toolchain. crosstool-NG can extract those options
288 to recreate a new configuration:
289 ct-ng extractconfig </path/to/your/build.log >.config
291 will extract those options, prompt you for the new ones, which you can later
292 edit with menuconfig.
294 Of course, if your build log was compressed, you'd have to use something like:
295 bzcat /path/to/your/build.log.bz2 |ct-ng extractconfig >.config
297 Then, once the configuration has been extracted, run:
300 ________________________
302 Running crosstool-NG /
303 _____________________/
305 To build the toolchain, simply type:
308 This will use the above configuration to retrieve, extract and patch the
309 components, build, install and eventually test your newly built toolchain.
311 You are then free to add the toolchain /bin directory in your PATH to use
314 In any case, you can get some terse help. Just type:
319 Stopping and restarting a build |
320 --------------------------------+
322 If you want to stop the build after a step you are debugging, you can pass the
323 variable STOP to make:
326 Conversely, if you want to restart a build at a specific step you are
327 debugging, you can pass the RESTART variable to make:
328 ct-ng RESTART=some_step
330 Alternatively, you can call make with the name of a step to just do that step:
333 ct-ng RESTART=libc_headers STOP=libc_headers
335 The shortcuts +step_name and step_name+ allow to respectively stop or restart
337 ct-ng +libc_headers and: ct-ng libc_headers+
339 ct-ng STOP=libc_headers and: ct-ng RESTART=libc_headers
341 To obtain the list of acceptable steps, please call:
344 Note that in order to restart a build, you'll have to say 'Y' to the config
345 option CT_DEBUG_CT_SAVE_STEPS, and that the previous build effectively went
348 Testing all toolchains at once |
349 -------------------------------+
351 You can test-build all samples; simply call:
354 Overriding the number of // jobs |
355 ---------------------------------+
357 If you want to override the number of jobs to run in // (the -j option to
358 make), you can either re-enter the menuconfig, or simply add it on the command
362 which tells crosstool-NG to override the number of // jobs to 4.
364 You can see the actions that support overriding the number of // jobs in
365 the help menu. Those are the ones with [.#] after them (eg. build[.#] or
366 regtest[.#], and so on...).
368 _______________________
370 Using the toolchain /
371 ____________________/
373 Using the toolchain is as simple as adding the toolchain's bin directory in
375 export PATH="${PATH}:/your/toolchain/path/bin"
377 and then using the target tuple to tell the build systems to use your
379 ./configure --target=your-target-tuple
381 make CC=your-target-tuple-gcc
383 make CROSS_COMPILE=your-target-tuple-
386 It is strongly advised not to use the toolchain sys-root directory as an
387 install directory for your programs/packages. If you do so, you will not be
388 able to use your toolchain for another project. It is even strongly advised
389 that your toolchain is chmod-ed to read-only once successfully build, so that
390 you don't go polluting your toolchain with your programs/packages' files.
392 Thus, when you build a program/package, install it in a separate directory,
393 eg. /your/root. This directory is the /image/ of what would be in the root file
394 system of your target, and will contain all that your programs/packages have
397 When your root directory is ready, it is still missing some important bits: the
398 toolchain's libraries. To populate your root directory with those libs, just
400 your-target-tuple-populate -s /your/root -d /your/root-populated
402 This will copy /your/root into /your/root-populated, and put the needed and only
403 the needed libraries there. Thus you don't polute /your/root with any cruft that
404 would no longer be needed should you have to remove stuff. /your/root always
405 contains only those things you install in it.
407 You can then use /your/root-populated to build up your file system image, a
408 tarball, or to NFS-mount it from your target, or whatever you need.
410 populate accepts the following options:
413 Use 'src_dir' as the 'source', un-populated root directory
416 Put the 'destination', populated root directory in 'dst_dir'
419 Remove 'dst_dir' if it previously existed
422 Be verbose, and tell what's going on (you can see exactly where libs are
433 There are four kinds of toolchains you could encounter.
435 First off, you must understand the following: when it comes to compilers there
436 are up to four machines involved:
437 1) the machine configuring the toolchain components: the config machine
438 2) the machine building the toolchain components: the build machine
439 3) the machine running the toolchain: the host machine
440 4) the machine the toolchain is generating code for: the target machine
442 We can most of the time assume that the config machine and the build machine
443 are the same. Most of the time, this will be true. The only time it isn't
444 is if you're using distributed compilation (such as distcc). Let's forget
445 this for the sake of simplicity.
447 So we're left with three machines:
452 Any toolchain will involve those three machines. You can be as pretty sure of
453 this as "2 and 2 are 4". Here is how they come into play:
455 1) build == host == target
456 This is a plain native toolchain, targetting the exact same machine as the
457 one it is built on, and running again on this exact same machine. You have
458 to build such a toolchain when you want to use an updated component, such
459 as a newer gcc for example.
460 crosstool-NG calls it "native".
462 2) build == host != target
463 This is a classic cross-toolchain, which is expected to be run on the same
464 machine it is compiled on, and generate code to run on a second machine,
466 crosstool-NG calls it "cross".
468 3) build != host == target
469 Such a toolchain is also a native toolchain, as it targets the same machine
470 as it runs on. But it is build on another machine. You want such a
471 toolchain when porting to a new architecture, or if the build machine is
472 much faster than the host machine.
473 crosstool-NG calls it "cross-native".
475 4) build != host != target
476 This one is called a canadian-toolchain (*), and is tricky. The three
477 machines in play are different. You might want such a toolchain if you
478 have a fast build machine, but the users will use it on another machine,
479 and will produce code to run on a third machine.
480 crosstool-NG calls it "canadian".
482 crosstool-NG can build all these kinds of toolchains (or is aiming at it,
485 (*) The term Canadian Cross came about because at the time that these issues
486 were all being hashed out, Canada had three national political parties.
487 http://en.wikipedia.org/wiki/Cross_compiler
494 Internally, crosstool-NG is script-based. To ease usage, the frontend is
500 The entry point to crosstool-NG is the Makefile script "ct-ng". Calling this
501 script with an action will act exactly as if the Makefile was in the current
502 working directory and make was called with the action as rule. Thus:
505 is equivalent to having the Makefile in CWD, and calling:
508 Having ct-ng as it is avoids copying the Makefile everywhere, and acts as a
511 ct-ng loads sub- Makefiles from the library directory $(CT_LIB_DIR), as set up
512 at configuration time with ./configure.
514 ct-ng also searches for config files, sub-tools, samples, scripts and patches in
515 that library directory.
517 Because of a stupid make behavior/bug I was unable to track down, implicit make
518 rules are disabled: installing with --local would triger those rules, and mconf
524 The kconfig language is a hacked version, vampirised from the toybox project
525 by Rob LANDLEY (http://www.landley.net/code/toybox/), itself coming from the
526 Linux kernel (http://www.kernel.org/), and (heavily) adapted to my needs.
528 The kconfig parsers (conf and mconf) are not installed pre-built, but as
529 source files. Thus you can have the directory where crosstool-NG is installed,
530 exported (via NFS or whatever) and have clients with different architectures
531 use the same crosstool-NG installation, and most notably, the same set of
534 Architecture-specific |
535 ----------------------+
537 Note: this chapter is not really well written, and might thus be a little bit
538 complex to understand. To get a better grasp of what an architecture is, the
539 reader is kindly encouraged to look at the "arch/" sub-directory, and to the
540 existing architectures to see how things are laid out.
542 An architecture is defined by:
544 - a human-readable name, in lower case letters, with numbers as appropriate.
545 The underscore is allowed; space and special characters are not.
547 - a directory in "arch/" named after the architecture, with the same letters
548 as above. Eg.: arch/arm, arch/x86_64
549 This directory contains the following files, and only those files:
550 - a configuration file in kconfig syntax, named "config.in", which shall
551 follow the API defined below.
552 Eg.: arch/arm/config.in
553 - a function script in bash-3.0 syntax, named "functions", which shall
554 follow the API defined below.
555 Eg.: arch/arm/functions
556 - an optional file, named "experimental" (in lower case!), which, if it
557 is present, means that support for this architecture is EXPERIMENTAL.
558 Eg.: arch/arm/experimental
560 The "config.in" file API:
561 > the config option "ARCH_%arch%" (where %arch% is to be replaced with the
562 actual architecture name).
563 That config option must have *neither* a type, *nor* a prompt! Also, it can
564 *not* depend on any other config option (EXPERIMENTAL is managed as above).
568 defines a (terse) help entry for this architecture:
572 The ARM architecture.
574 selects adequate associated config options.
577 select ARCH_SUPPORTS_BOTH_ENDIAN
578 select ARCH_DEFAULT_LE
580 The ARM architecture.
582 > other target-specific options, at your discretion. Note however that to
583 avoid name-clashing, such options shall be prefixed with "ARCH_%arch%",
584 where %arch% is again replaced by the actual architecture name.
585 (Note: due to historical reasons, and lack of time to clean up the code,
586 I may have left some config options that do not completely conform to
587 this, as the architecture name was written all upper case. However, the
588 prefix is unique among architectures, and does not cause harm).
590 The "functions" file API:
591 > the function "CT_DoArchValues"
594 - all variables from the ".config" file,
595 - the two variables "target_endian_eb" and "target_endian_el" which are
596 the endianness suffixes
597 + return value: 0 upon success, !0 upon failure
600 - the environment variable CT_TARGET_ARCH
602 the architecture part of the target tuple.
603 Eg.: "armeb" for big endian ARM
607 - the environment variable CT_TARGET_SYS
609 the sytem part of the target tuple.
610 Eg.: "gnu" for glibc on most architectures
611 "gnueabi" for glibc on an ARM EABI
613 - for glibc-based toolchain: "gnu"
614 - for uClibc-based toolchain: "uclibc"
617 - the environment variable CT_KERNEL_ARCH
619 the architecture name as understandable by the Linux kernel build
621 Eg.: "arm" for an ARM
622 "powerpc" for a PowerPC
628 - the environment variables to configure the cross-gcc (defaults)
629 - CT_ARCH_WITH_ARCH : the gcc ./configure switch to select architecture level ( "--with-arch=${CT_ARCH_ARCH}" )
630 - CT_ARCH_WITH_ABI : the gcc ./configure switch to select ABI level ( "--with-abi=${CT_ARCH_ABI}" )
631 - CT_ARCH_WITH_CPU : the gcc ./configure switch to select CPU instruction set ( "--with-cpu=${CT_ARCH_CPU}" )
632 - CT_ARCH_WITH_TUNE : the gcc ./configure switch to select scheduling ( "--with-tune=${CT_ARCH_TUNE}" )
633 - CT_ARCH_WITH_FPU : the gcc ./configure switch to select FPU type ( "--with-fpu=${CT_ARCH_FPU}" )
634 - CT_ARCH_WITH_FLOAT : the gcc ./configure switch to select floating point arithmetics ( "--with-float=soft" or /empty/ )
637 - the environment variables to pass to the cross-gcc to build target binaries (defaults)
638 - CT_ARCH_ARCH_CFLAG : the gcc switch to select architecture level ( "-march=${CT_ARCH_ARCH}" )
639 - CT_ARCH_ABI_CFLAG : the gcc switch to select ABI level ( "-mabi=${CT_ARCH_ABI}" )
640 - CT_ARCH_CPU_CFLAG : the gcc switch to select CPU instruction set ( "-mcpu=${CT_ARCH_CPU}" )
641 - CT_ARCH_TUNE_CFLAG : the gcc switch to select scheduling ( "-mtune=${CT_ARCH_TUNE}" )
642 - CT_ARCH_FPU_CFLAG : the gcc switch to select FPU type ( "-mfpu=${CT_ARCH_FPU}" )
643 - CT_ARCH_FLOAT_CFLAG : the gcc switch to choose floating point arithmetics ( "-msoft-float" or /empty/ )
644 - CT_ARCH_ENDIAN_CFLAG : the gcc switch to choose big or little endian ( "-mbig-endian" or "-mlittle-endian" )
649 - the environement variables to configure the core and final compiler, specific to this architecture:
650 - CT_ARCH_CC_CORE_EXTRA_CONFIG : additional, architecture specific core gcc ./configure flags
651 - CT_ARCH_CC_EXTRA_CONFIG : additional, architecture specific final gcc ./configure flags
656 - the architecture-specific CFLAGS and LDFLAGS:
657 - CT_ARCH_TARGET_CLFAGS
658 - CT_ARCH_TARGET_LDFLAGS
662 Adding a new version of a component |
663 ------------------------------------+
665 When a new component, such as the Linux kernel, gcc or any other is released,
666 adding the new version to crosstool-NG is quite easy. There is a script that
667 will do all that for you:
668 tools/addToolVersion.sh
670 Run it with no option to get some help.
675 To Be Written later...