Ignore generated paths.mk.
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
17 Preparing for packaging
20 Configuring crosstool-NG
21 Interesting config options
22 Re-building an existing toolchain
24 Stopping and restarting a build
25 Testing all toolchains at once
26 Overriding the number of // jobs
33 Adding a new version of a component
41 crosstool-NG aims at building toolchains. Toolchains are an essential component
42 in a software development project. It will compile, assemble and link the code
43 that is being developed. Some pieces of the toolchain will eventually end up
44 in the resulting binary/ies: static libraries are but an example.
46 So, a toolchain is a very sensitive piece of software, as any bug in one of the
47 components, or a poorly configured component, can lead to execution problems,
48 ranging from poor performance, to applications ending unexpectedly, to
49 mis-behaving software (which more than often is hard to detect), to hardware
50 damage, or even to human risks (which is more than regrettable).
52 Toolchains are made of different piece of software, each being quite complex
53 and requiring specially crafted options to build and work seamlessly. This
54 is usually not that easy, even in the not-so-trivial case of native toolchains.
55 The work reaches a higher degree of complexity when it comes to cross-
56 compilation, where it can become quite a nightmare...
58 Some cross-toolchains exist on the internet, and can be used for general
59 development, but they have a number of limitations:
60 - they can be general purpose, in that they are configured for the majority:
61 no optimisation for your specific target,
62 - they can be prepared for a specific target and thus are not easy to use,
63 nor optimised for, or even supporting your target,
64 - they often are using aging components (compiler, C library, etc...) not
65 supporting special features of your shiny new processor;
66 On the other side, these toolchain offer some advantages:
67 - they are ready to use and quite easy to install and setup,
68 - they are proven if used by a wide community.
70 But once you want to get all the juice out of your specific hardware, you will
71 want to build your own toolchain. This is where crosstool-NG comes into play.
73 There are also a number of tools that build toolchains for specific needs,
74 which are not really scalable. Examples are:
75 - buildroot (buildroot.uclibc.org) whose main purpose is to build root file
76 systems, hence the name. But once you have your toolchain with buildroot,
77 part of it is installed in the root-to-be, so if you want to build a whole
78 new root, you either have to save the existing one as a template and
79 restore it later, or restart again from scratch. This is not convenient,
80 - ptxdist (www.pengutronix.de/software/ptxdist), whose purpose is very
82 - other projects (openembedded.org for example), which are again used to
83 build root file systems.
85 crosstool-NG is really targeted at building toolchains, and only toolchains.
86 It is then up to you to use it the way you want.
93 crosstool was first 'conceived' by Dan Kegel, who offered it to the community
94 as a set of scripts, a repository of patches, and some pre-configured, general
95 purpose setup files to be used to configure crosstool. This is available at
96 http://www.kegel.com/crosstool, and the subversion repository is hosted on
97 google at http://code.google.com/p/crosstool/.
99 I once managed to add support for uClibc-based toolchains, but it did not make
100 into mainline, mostly because I didn't have time to port the patch forward to
101 the new versions, due in part to the big effort it was taking.
103 So I decided to clean up crosstool in the state it was, re-order the things
104 in place, add appropriate support for what I needed, that is uClibc support
105 and a menu-driven configuration, named the new implementation crosstool-NG,
106 (standing for crosstool Next Generation, as many other comunity projects do,
107 and as a wink at the TV series "Star Trek: The Next Generation" ;-) ) and
108 made it available to the community, in case it was of interest to any one.
110 ___________________________
112 Installing crosstool-NG /
113 ________________________/
115 There are two ways you can use crosstool-NG:
116 - build and install it, then get rid of the sources like you'd do for most
118 - or only build it and run from the source directory.
120 The former should be used if you got crosstool-NG from a packaged tarball, see
121 "Install method", below, while the latter is most useful for developpers that
122 checked the code out from SVN, and want to submit patches, see "The Hacker's
128 If you go for the install, then you just follow the classical, but yet easy
130 ./configure --prefix=/some/place
133 export PATH="${PATH}:/some/place/bin"
135 You can then get rid of crosstool-NG source. Next create a directory to serve
136 as a working place, cd in there and run:
139 See below for complete usage.
144 If you go the hacker's way, then the usage is a bit different, although very
150 Now, *do not* remove crosstool-NG sources. They are needed to run crosstool-NG!
151 Stay in the directory holding the sources, and run:
154 See below for complete usage.
156 Now, provided you checked-out the code, you can send me your interesting changes
160 and mailing me the result! :-P
162 Preparing for packaging |
163 ------------------------+
165 If you plan on packaging crosstool-NG, you surely don't want to install it
166 in your root file system. The install procedure of crosstool-NG honors the
169 ./configure --prefix=/usr
171 make DESDTDIR=/packaging/place install
176 crosstool-NG comes with a shell script fragment that defines bash-compatible
177 completion. That shell fragment is currently not installed automatically, but
180 To install the shell script fragment, you have two options:
181 - install system-wide, most probably by copying ct-ng.comp into
182 /etc/bash_completion.d/
183 - install for a single user, by copying ct-ng.comp into ${HOME}/ and
184 sourcing this file from your ${HOME}/.bashrc
189 Some people contibuted code that couldn't get merged for various reasons. This
190 code is available as patches in the contrib/ sub-directory. These patches are
191 to be applied to the source of crosstool-NG, prior to installing.
193 An easy way to use contributed code is to pass the --with-contrib= option to
194 ./configure. The possible values depend upon which contributions are packaged
195 with your version, but you can get with it with passing one of those two
198 will list all available contributions
201 will select all avalaible contributions
203 There is no guarantee that a particuliar contribution applies to the current
204 version of crosstool-ng, or that it will work at all. Use contributions at
207 ____________________________
209 Configuring crosstool-NG /
210 _________________________/
212 crosstool-NG is configured with a configurator presenting a menu-stuctured set
213 of options. These options let you specify the way you want your toolchain
214 built, where you want it installed, what architecture and specific processor it
215 will support, the version of the components you want to use, etc... The
216 value for those options are then stored in a configuration file.
218 The configurator works the same way you configure your Linux kernel. It is
219 assumed you now how to handle this.
221 To enter the menu, type:
224 Almost every config item has a help entry. Read them carefully.
226 String and number options can refer to environment variables. In such a case,
227 you must use the shell syntax: ${VAR}. You shall neither single- nor double-
228 quote the string/number options.
230 There are three environment variables that are computed by crosstool-NG, and
234 It represents the target tuple you are building for. You can use it for
235 example in the installation/prefix directory, such as:
236 /opt/x-tools/${CT_TARGET}
239 The top directory where crosstool-NG is running. You shouldn't need it in
240 most cases. There is one case where you may need it: if you have local
241 patches and you store them in your running directory, you can refer to them
242 by using CT_TOP_DIR, such as:
243 ${CT_TOP_DIR}/patches.myproject
246 The version of crosstool-NG you are using. Not much use for you, but it's
247 there if you need it.
249 Interesting config options |
250 ---------------------------+
252 CT_LOCAL_TARBALLS_DIR:
253 If you already have some tarballs in a direcotry, enter it here. That will
254 speed up the retrieving phase, where crosstool-NG would otherwise download
258 This is where the toolchain will be installed in (and for now, where it
259 will run from). Common use is to add the target tuple in the directory
260 path, such as (see above):
261 /opt/x-tools/${CT_TARGET}
264 An identifier for your toolchain, will take place in the vendor part of the
265 target tuple. It shall *not* contain spaces or dashes. Usually, keep it
266 to a one-word string, or use underscores to separate words if you need.
267 Avoid dots, commas, and special characters.
270 An alias for the toolchian. It will be used as a prefix to the toolchain
271 tools. For example, you will have ${CT_TARGET_ALIAS}-gcc
273 Also, if you think you don't see enough versions, you can try to enable one of
277 Show obsolete versions or tools. Most of the time, you don't want to base
278 your toolchain on too old a version (of gcc, for example). But at times, it
279 can come handy to use such an old version for regression tests. Those old
280 versions are hidden behind CT_OBSOLETE.
283 Show experimental versions or tools. Again, you might not want to base your
284 toolchain on too recent tools (eg. gcc) for production. But if you need a
285 feature present only in a recent version, or a new tool, you can find them
286 hidden behind CT_EXPERIMENTAL.
288 Re-building an existing toolchain |
289 ----------------------------------+
291 If you have an existing toolchain, you can re-use the options used to build it
292 to create a new toolchain. That needs a very little bit of effort on your side
293 but is quite easy. The options to build a toolchain are saved with the
294 toolchain, and you can retrieve this configuration by running:
297 This will dump the configuration to stdout, so to rebuild a toolchain with this
298 configuration, the following is all you need to do:
299 ${CT_TARGET}-config >.config
302 Then, you can review and change the configuration by running:
305 ________________________
307 Running crosstool-NG /
308 _____________________/
310 To build the toolchain, simply type:
313 This will use the above configuration to retrieve, extract and patch the
314 components, build, install and eventually test your newly built toolchain.
316 You are then free to add the toolchain /bin directory in your PATH to use
319 In any case, you can get some terse help. Just type:
324 Stopping and restarting a build |
325 --------------------------------+
327 If you want to stop the build after a step you are debugging, you can pass the
328 variable STOP to make:
331 Conversely, if you want to restart a build at a specific step you are
332 debugging, you can pass the RESTART variable to make:
333 ct-ng RESTART=some_step
335 Alternatively, you can call make with the name of a step to just do that step:
338 ct-ng RESTART=libc_headers STOP=libc_headers
340 The shortcuts +step_name and step_name+ allow to respectively stop or restart
342 ct-ng +libc_headers and: ct-ng libc_headers+
344 ct-ng STOP=libc_headers and: ct-ng RESTART=libc_headers
346 To obtain the list of acceptable steps, please call:
349 Note that in order to restart a build, you'll have to say 'Y' to the config
350 option CT_DEBUG_CT_SAVE_STEPS, and that the previous build effectively went
353 Building all toolchains at once |
354 --------------------------------+
356 You can build all samples; simply call:
359 Overriding the number of // jobs |
360 ---------------------------------+
362 If you want to override the number of jobs to run in // (the -j option to
363 make), you can either re-enter the menuconfig, or simply add it on the command
367 which tells crosstool-NG to override the number of // jobs to 4.
369 You can see the actions that support overriding the number of // jobs in
370 the help menu. Those are the ones with [.#] after them (eg. build[.#] or
371 build-all[.#], and so on...).
376 The crosstool-NG script 'ct-ng' is a Makefile-script. It does *not* execute
377 in parallel (there is not much to gain). When speaking of // jobs, we are
378 refering to the number of // jobs when making the *components*. That is, we
379 speak of the number of // jobs used to build gcc, glibc, and so on...
382 _______________________
384 Using the toolchain /
385 ____________________/
387 Using the toolchain is as simple as adding the toolchain's bin directory in
389 export PATH="${PATH}:/your/toolchain/path/bin"
391 and then using the target tuple to tell the build systems to use your
393 ./configure --target=your-target-tuple
395 make CC=your-target-tuple-gcc
397 make CROSS_COMPILE=your-target-tuple-
400 It is strongly advised not to use the toolchain sys-root directory as an
401 install directory for your programs/packages. If you do so, you will not be
402 able to use your toolchain for another project. It is even strongly advised
403 that your toolchain is chmod-ed to read-only once successfully build, so that
404 you don't go polluting your toolchain with your programs/packages' files.
406 Thus, when you build a program/package, install it in a separate directory,
407 eg. /your/root. This directory is the /image/ of what would be in the root file
408 system of your target, and will contain all that your programs/packages have
411 When your root directory is ready, it is still missing some important bits: the
412 toolchain's libraries. To populate your root directory with those libs, just
414 your-target-tuple-populate -s /your/root -d /your/root-populated
416 This will copy /your/root into /your/root-populated, and put the needed and only
417 the needed libraries there. Thus you don't polute /your/root with any cruft that
418 would no longer be needed should you have to remove stuff. /your/root always
419 contains only those things you install in it.
421 You can then use /your/root-populated to build up your file system image, a
422 tarball, or to NFS-mount it from your target, or whatever you need.
424 populate accepts the following options:
427 Use 'src_dir' as the 'source', un-populated root directory
430 Put the 'destination', populated root directory in 'dst_dir'
433 Remove 'dst_dir' if it previously existed
436 Be verbose, and tell what's going on (you can see exactly where libs are
447 There are four kinds of toolchains you could encounter.
449 First off, you must understand the following: when it comes to compilers there
450 are up to four machines involved:
451 1) the machine configuring the toolchain components: the config machine
452 2) the machine building the toolchain components: the build machine
453 3) the machine running the toolchain: the host machine
454 4) the machine the toolchain is generating code for: the target machine
456 We can most of the time assume that the config machine and the build machine
457 are the same. Most of the time, this will be true. The only time it isn't
458 is if you're using distributed compilation (such as distcc). Let's forget
459 this for the sake of simplicity.
461 So we're left with three machines:
466 Any toolchain will involve those three machines. You can be as pretty sure of
467 this as "2 and 2 are 4". Here is how they come into play:
469 1) build == host == target
470 This is a plain native toolchain, targetting the exact same machine as the
471 one it is built on, and running again on this exact same machine. You have
472 to build such a toolchain when you want to use an updated component, such
473 as a newer gcc for example.
474 crosstool-NG calls it "native".
476 2) build == host != target
477 This is a classic cross-toolchain, which is expected to be run on the same
478 machine it is compiled on, and generate code to run on a second machine,
480 crosstool-NG calls it "cross".
482 3) build != host == target
483 Such a toolchain is also a native toolchain, as it targets the same machine
484 as it runs on. But it is build on another machine. You want such a
485 toolchain when porting to a new architecture, or if the build machine is
486 much faster than the host machine.
487 crosstool-NG calls it "cross-native".
489 4) build != host != target
490 This one is called a canadian-toolchain (*), and is tricky. The three
491 machines in play are different. You might want such a toolchain if you
492 have a fast build machine, but the users will use it on another machine,
493 and will produce code to run on a third machine.
494 crosstool-NG calls it "canadian".
496 crosstool-NG can build all these kinds of toolchains (or is aiming at it,
499 (*) The term Canadian Cross came about because at the time that these issues
500 were all being hashed out, Canada had three national political parties.
501 http://en.wikipedia.org/wiki/Cross_compiler
508 Internally, crosstool-NG is script-based. To ease usage, the frontend is
514 The entry point to crosstool-NG is the Makefile script "ct-ng". Calling this
515 script with an action will act exactly as if the Makefile was in the current
516 working directory and make was called with the action as rule. Thus:
519 is equivalent to having the Makefile in CWD, and calling:
522 Having ct-ng as it is avoids copying the Makefile everywhere, and acts as a
525 ct-ng loads sub- Makefiles from the library directory $(CT_LIB_DIR), as set up
526 at configuration time with ./configure.
528 ct-ng also searches for config files, sub-tools, samples, scripts and patches in
529 that library directory.
531 Because of a stupid make behavior/bug I was unable to track down, implicit make
532 rules are disabled: installing with --local would triger those rules, and mconf
538 The kconfig language is a hacked version, vampirised from the Linux kernel
539 (http://www.kernel.org/), and (heavily) adapted to my needs.
541 The list of the most notable changes (at least the ones I remember) follows:
542 - the CONFIG_ prefix has been replaced with CT_
543 - a leading | in prompts is skipped, and subsequent leading spaces are not
545 - otherwise leading spaces are silently trimmed
547 The kconfig parsers (conf and mconf) are not installed pre-built, but as
548 source files. Thus you can have the directory where crosstool-NG is installed,
549 exported (via NFS or whatever) and have clients with different architectures
550 use the same crosstool-NG installation, and most notably, the same set of
553 Architecture-specific |
554 ----------------------+
556 Note: this chapter is not really well written, and might thus be a little bit
557 complex to understand. To get a better grasp of what an architecture is, the
558 reader is kindly encouraged to look at the "arch/" sub-directory, and to the
559 existing architectures to see how things are laid out.
561 An architecture is defined by:
563 - a human-readable name, in lower case letters, with numbers as appropriate.
564 The underscore is allowed; space and special characters are not.
566 - a file in "config/arch/", named after the architecture's name, and suffixed
568 Eg.: config/arch/arm.in
569 - a file in "scripts/build/arch/", named after the architecture's name, and
571 Eg.: scripts/build/arch/arm.sh
573 The architecture's ".in" file API:
574 > the config option "ARCH_%arch%" (where %arch% is to be replaced with the
575 actual architecture name).
576 That config option must have *neither* a type, *nor* a prompt! Also, it can
577 *not* depend on any other config option (EXPERIMENTAL is managed as above).
581 defines a (terse) help entry for this architecture:
585 The ARM architecture.
587 selects adequate associated config options.
588 Note: 64-bit architectures *shall* select ARCH_64
591 select ARCH_SUPPORTS_BOTH_ENDIAN
592 select ARCH_DEFAULT_LE
594 The ARM architecture.
599 The x86_64 architecture.
601 > other target-specific options, at your discretion. Note however that to
602 avoid name-clashing, such options shall be prefixed with "ARCH_%arch%",
603 where %arch% is again replaced by the actual architecture name.
604 (Note: due to historical reasons, and lack of time to clean up the code,
605 I may have left some config options that do not completely conform to
606 this, as the architecture name was written all upper case. However, the
607 prefix is unique among architectures, and does not cause harm).
609 The architecture's ".sh" file API:
610 > the function "CT_DoArchTupleValues"
613 - all variables from the ".config" file,
614 - the two variables "target_endian_eb" and "target_endian_el" which are
615 the endianness suffixes
616 + return value: 0 upon success, !0 upon failure
619 - the environment variable CT_TARGET_ARCH
621 the architecture part of the target tuple.
622 Eg.: "armeb" for big endian ARM
626 - the environment variable CT_TARGET_SYS
628 the sytem part of the target tuple.
629 Eg.: "gnu" for glibc on most architectures
630 "gnueabi" for glibc on an ARM EABI
632 - for glibc-based toolchain: "gnu"
633 - for uClibc-based toolchain: "uclibc"
636 - the environment variable CT_KERNEL_ARCH
638 the architecture name as understandable by the Linux kernel build
640 Eg.: "arm" for an ARM
641 "powerpc" for a PowerPC
647 - the environment variables to configure the cross-gcc (defaults)
648 - CT_ARCH_WITH_ARCH : the gcc ./configure switch to select architecture level ( "--with-arch=${CT_ARCH_ARCH}" )
649 - CT_ARCH_WITH_ABI : the gcc ./configure switch to select ABI level ( "--with-abi=${CT_ARCH_ABI}" )
650 - CT_ARCH_WITH_CPU : the gcc ./configure switch to select CPU instruction set ( "--with-cpu=${CT_ARCH_CPU}" )
651 - CT_ARCH_WITH_TUNE : the gcc ./configure switch to select scheduling ( "--with-tune=${CT_ARCH_TUNE}" )
652 - CT_ARCH_WITH_FPU : the gcc ./configure switch to select FPU type ( "--with-fpu=${CT_ARCH_FPU}" )
653 - CT_ARCH_WITH_FLOAT : the gcc ./configure switch to select floating point arithmetics ( "--with-float=soft" or /empty/ )
656 - the environment variables to pass to the cross-gcc to build target binaries (defaults)
657 - CT_ARCH_ARCH_CFLAG : the gcc switch to select architecture level ( "-march=${CT_ARCH_ARCH}" )
658 - CT_ARCH_ABI_CFLAG : the gcc switch to select ABI level ( "-mabi=${CT_ARCH_ABI}" )
659 - CT_ARCH_CPU_CFLAG : the gcc switch to select CPU instruction set ( "-mcpu=${CT_ARCH_CPU}" )
660 - CT_ARCH_TUNE_CFLAG : the gcc switch to select scheduling ( "-mtune=${CT_ARCH_TUNE}" )
661 - CT_ARCH_FPU_CFLAG : the gcc switch to select FPU type ( "-mfpu=${CT_ARCH_FPU}" )
662 - CT_ARCH_FLOAT_CFLAG : the gcc switch to choose floating point arithmetics ( "-msoft-float" or /empty/ )
663 - CT_ARCH_ENDIAN_CFLAG : the gcc switch to choose big or little endian ( "-mbig-endian" or "-mlittle-endian" )
668 - the environement variables to configure the core and final compiler, specific to this architecture:
669 - CT_ARCH_CC_CORE_EXTRA_CONFIG : additional, architecture specific core gcc ./configure flags
670 - CT_ARCH_CC_EXTRA_CONFIG : additional, architecture specific final gcc ./configure flags
675 - the architecture-specific CFLAGS and LDFLAGS:
676 - CT_ARCH_TARGET_CLFAGS
677 - CT_ARCH_TARGET_LDFLAGS
681 You can have a look at "config/arch/arm.in" and "scripts/build/arch/arm.sh" for
682 a quite complete example of what an actual architecture description looks like.
687 A kernel is defined by:
689 - a human-readable name, in lower case letters, with numbers as appropriate.
690 The underscore is allowed; space and special characters are not (although
691 they are internally replaced with underscores.
692 Eg.: linux, bare-metal
693 - a file in "config/kernel/", named after the kernel name, and suffixed with
695 Eg.: config/kernel/linux.in, config/kernel/bare-metal.in
696 - a file in "scripts/build/kernel/", named after the kernel name, and suffixed
698 Eg.: scripts/build/kernel/linux.sh, scripts/build/kernel/bare-metal.sh
700 The kernel's ".in" file must contain:
701 > an optional lines containing exactly "# EXPERIMENTAL", starting on the
702 first column, and without any following space or other character.
703 If this line is present, then this kernel is considered EXPERIMENTAL,
704 and correct dependency on EXPERIMENTAL will be set.
706 > the config option "KERNEL_%kernel_name%" (where %kernel_name% is to be
707 replaced with the actual kernel name, with all special characters and
708 spaces replaced by underscores).
709 That config option must have *neither* a type, *nor* a prompt! Also, it can
710 *not* depends on EXPERIMENTAL.
711 Eg.: KERNEL_linux, KERNEL_bare_metal
713 defines a (terse) help entry for this kernel.
715 config KERNEL_bare_metal
717 Build a compiler for use without any kernel.
719 selects adequate associated config options.
721 config KERNEL_bare_metal
724 Build a compiler for use without any kernel.
726 > other kernel specific options, at your discretion. Note however that, to
727 avoid name-clashing, such options should be prefixed with
728 "KERNEL_%kernel_name%", where %kernel_name% is again tp be replaced with
729 the actual kernel name.
730 (Note: due to historical reasons, and lack of time to clean up the code,
731 I may have left some config options that do not completely conform to
732 this, as the kernel name was written all upper case. However, the prefix
733 is unique among kernels, and does not cause harm).
735 The kernel's ".sh" file API:
736 > is a bash script fragment
738 > defines the function CT_DoKernelTupleValues
739 + see the architecture's CT_DoArchTupleValues, except for:
740 + set the environment variable CT_TARGET_KERNEL, the kernel part of the
742 + return value: ignored
744 > defines the function "do_kernel_get":
747 - all variables from the ".config" file.
748 + return value: 0 for success, !0 for failure.
749 + behavior: download the kernel's sources, and store the tarball into
750 "${CT_TARBALLS_DIR}". To this end, a functions is available, that
751 abstracts downloading tarballs:
752 - CT_DoGet <tarball_base_name> <URL1 [URL...]>
753 Eg.: CT_DoGet linux-2.6.26.5 ftp://ftp.kernel.org/pub/linux/kernel/v2.6
754 Note: retrieving sources from svn, cvs, git and the likes is not supported
755 by CT_DoGet. You'll have to do this by hand, as it is done for eglibc in
756 "scripts/build/libc/eglibc.sh"
758 > defines the function "do_kernel_extract":
761 - all variables from the ".config" file,
762 + return value: 0 for success, !0 for failure.
763 + behavior: extract the kernel's tarball into "${CT_SRC_DIR}", and apply
764 required patches. To this end, a function is available, that abstracts
766 - CT_ExtractAndPatch <tarball_base_name>
767 Eg.: CT_ExtractAndPatch linux-2.6.26.5
769 > defines the function "do_kernel_headers":
772 - all variables from the ".config" file,
773 + return value: 0 for success, !0 for failure.
774 + behavior: install the kernel headers (if any) in "${CT_SYSROOT_DIR}/usr/include"
776 > defines any kernel-specific helper functions
777 These functions, if any, must be prefixed with "do_kernel_%CT_KERNEL%_",
778 where '%CT_KERNEL%' is to be replaced with the actual kernel name, to avoid
781 You can have a look at "config/kernel/linux.in" and "scripts/build/kernel/linux.sh"
782 as an example of what a complex kernel description looks like.
784 Adding a new version of a component |
785 ------------------------------------+
787 When a new component, such as the Linux kernel, gcc or any other is released,
788 adding the new version to crosstool-NG is quite easy. There is a script that
789 will do all that for you:
790 scripts/addToolVersion.sh
792 Run it with no option to get some help.
797 To Be Written later...