Toolchains - Revision history

Ymorin: Update crosstool-NG home

2013-01-25T21:13:50Z

Update crosstool-NG home

Michael Opdenacker: /* Linaro (ARM) */ Added a link to the Linaro Toolchains page

2011-10-27T12:17:50Z

‎Linaro (ARM): Added a link to the Linaro Toolchains page

Michael Opdenacker: /* Crosstool */ Removed - Replaced by Crosstool-ng

2011-10-27T12:13:24Z

‎Crosstool: Removed - Replaced by Crosstool-ng

Michael Opdenacker: /* Linaro (ARM) */ Mentioned Linux source toolchains

2011-10-27T11:23:44Z

‎Linaro (ARM): Mentioned Linux source toolchains

Michael Opdenacker: /* Prebuilt toolchains */ Added LInaro toolchains

2011-10-27T11:05:34Z

‎Prebuilt toolchains: Added LInaro toolchains

Jrspruitt: /* Getting a toolchain */

2011-07-05T07:31:37Z

‎Getting a toolchain

Radhermit: Insert space for sentence

2011-04-13T03:16:53Z

Insert space for sentence

Radhermit: Use link with accented characters

2011-04-13T03:16:13Z

Use link with accented characters

Radhermit: Update Gentoo crossdev link

2011-04-13T03:13:52Z

Update Gentoo crossdev link

Fxkuehl: /* C library */ Add a a reference to EGLIBC

2011-04-12T00:34:09Z

‎C library: Add a a reference to EGLIBC

@@ Line 123: / Line 123: @@
 ==== Crosstool-NG ====
-[http://ymorin.is-a-geek.org/projects/crosstool Crosstool-NG] is a well-maintained fork of crosstool, targeted at easier configuration, re-factored code, and a learning base on how toolchains are built, with support for both uClibc and glibc, for debug tools (gdb, strace, dmalloc...), and a wide range of versions for each tools. Different target architectures are supported as well. It offers a kernel-like configuration system to select the different configuration options of the toolchain (component versions, component configuration, etc.). Crosstool-NG has an active and responsive user and developer community.
+[http://crosstool-ng.org/ Crosstool-NG] is a well-maintained fork of crosstool, targeted at easier configuration, re-factored code, and a learning base on how toolchains are built, with support for both uClibc and glibc, for debug tools (gdb, strace, dmalloc...), and a wide range of versions for each tools. Different target architectures are supported as well. It offers a kernel-like configuration system to select the different configuration options of the toolchain (component versions, component configuration, etc.). Crosstool-NG has an active and responsive user and developer community.
 ==== Crossdev/tsrpm (Timesys) ====

@@ Line 57: / Line 57: @@
 ==== Linaro (ARM) ====
-[http://linaro.org/ Linaro] releases optimized binary toolchains for recent ARM CPUs (Cortex A8, A9...). These include Linaro's latest contributions to mainline gcc, but backported to stable gcc versions for immediate use by product developers. Linaro actually hires CodeSourcery people to improve ARM toolchains, so the ARM toolchains that you get with Linaro should be at least as good as the CodeSourcery ones.
+[http://linaro.org/ Linaro] releases [https://wiki.linaro.org/WorkingGroups/ToolChain optimized toolchains] for recent ARM CPUs (Cortex A8, A9...). These include Linaro's latest contributions to mainline gcc, but backported to stable gcc versions for immediate use by product developers. Linaro actually hires CodeSourcery people to improve ARM toolchains, so the ARM toolchains that you get with Linaro should be at least as good as the CodeSourcery ones.
 Native toolchains are available through the standard gcc toolchain in Ubuntu. Cross toolchains are available to Ubuntu users through special packages:

@@ Line 121: / Line 121: @@
 ==== Crossdev (Gentoo) ====
 Crossdev is specific to developers using Gentoo for their development PCs. It is a script which generates a cross toolchain using the portage build scripts for gcc etc. There are numerous architectures which are supported and both uClibc and glibc toolchains can be built. Link: [http://en.gentoo-wiki.com/wiki/Crossdev Gentoo Crossdev info]
 ==== Crosstool-NG ====

@@ Line 71: / Line 71: @@
 dpkg -L gcc-arm-linux-gnueabi
 </pre>
 ==== DENX ELDK ====

@@ Line 54: / Line 54: @@
 ==== CodeSourcery ====
 [http://www.codesourcery.com/ CodeSourcery] develops [http://www.codesourcery.com/gnu_toolchains/sgpp/ Sourcery G++], an [http://en.wikipedia.org/wiki/Eclipse_IDE Eclipse] based [http://en.wikipedia.org/wiki/Integrated_development_environment Integrated Development Environment (IDE)] that incorporates the [http://en.wikipedia.org/wiki/GNU_toolchain GNU Toolchain] (gcc, gdb, etc.) for cross development for numerous target architectures. [http://www.codesourcery.com/ CodeSourcery] provides a "lite" version for [http://www.codesourcery.com/gnu_toolchains/arm ARM], [http://www.codesourcery.com/gnu_toolchains/coldfire Coldfire], [http://www.codesourcery.com/gnu_toolchains/mips MIPS],  [http://www.codesourcery.com/gnu_toolchains/sgpp/lite/superh SuperH] and [http://www.codesourcery.com/gnu_toolchains/power Power] architectures. The toolchains are always very up to date. [http://www.codesourcery.com/ CodeSourcery] contributes enhancements it makes to the [http://en.wikipedia.org/wiki/GNU_toolchain GNU Toolchain] upstream continually, making it the single largest (by patch count) corporate contributor.
 ==== DENX ELDK ====
@@ Line 94: / Line 111: @@
 ('emchain' to build your own version of current toolchain,
 should a suitable pre-built one not exist.
 === Toolchain building systems ===

@@ Line 46: / Line 46: @@
 There are several ways to get a toolchain :
-* Get a prebuilt toolchain, either from a vendor such as [http://www.codesourcery.com/ CodeSourcery], or probably inside the [http://en.wikipedia.org/wiki/Board_support_package Board Support Package] shipped with your hardware platform by the vendor. This is the easiest solution, as the toolchain is already built, and has supposedly being tested by the vendor. The drawback is that you don't have flexibility on your toolchain features (which C library ? hard-float or soft-float ? which ABI ?)
+* Get a prebuilt toolchain, either from a vendor such as [http://www.codesourcery.com/ CodeSourcery], or probably inside the [http://en.wikipedia.org/wiki/Board_support_package Board Support Package] shipped with your hardware platform by the vendor. This is the easiest solution, as the toolchain is already built, and has supposedly been tested by the vendor. The drawback is that you don't have flexibility on your toolchain features (which C library ? hard-float or soft-float ? which ABI ?)
 * Build a toolchain on your own. However, this can be a real pain. There are version dependency issues, patches required to make something work etc. etc. Check out this (obsolete) [http://kegel.com/crosstool/crosstool-0.43/buildlogs/ build matrix] for crosstool and look at all the red "failed" entries.
 * Build a toolchain using an automated tool. The community has built several scripts or more elaborate systems to ease the process of building a toolchain. This way, the recipes and patches needed to build a toolchain made of particular versions of the various components are shared and easily available.

@@ Line 140: / Line 140: @@
 ==== Bitbake ====
-Bitbake is the tool used by [http://wiki.openembedded.net/index.php/Main_Page OpenEmbedded].The best way to get started is probably by just building an existing distribution that uses openembedded (e.g. Ångström, see http://www.angstrom-distribution.org/building-ångström for details).
+Bitbake is the tool used by [http://wiki.openembedded.net/index.php/Main_Page OpenEmbedded]. The best way to get started is probably by just building an existing distribution that uses openembedded (e.g. Ångström, see http://www.angstrom-distribution.org/building-ångström for details).
 == By Platform ==

@@ Line 102: / Line 102: @@
 ==== Crossdev (Gentoo) ====
-Crossdev is specific to developers using Gentoo for their development PCs. It is a script which generates a cross toolchain using the portage build scripts for gcc etc. There are numerous architectures which are supported and both uClibc and glibc toolchains can be built. Link: [http://gentoo-wiki.com/HOWTO_Cross_Compile Gentoo Cross-Compile HOWTO]
+Crossdev is specific to developers using Gentoo for their development PCs. It is a script which generates a cross toolchain using the portage build scripts for gcc etc. There are numerous architectures which are supported and both uClibc and glibc toolchains can be built. Link: [http://en.gentoo-wiki.com/wiki/Crossdev Gentoo Crossdev info]
 ==== Crosstool ====

@@ Line 34: / Line 34: @@
 Realistically, there are nowadays two options for the C Library:
 * [http://en.wikipedia.org/wiki/Glibc glibc] is the C library from the GNU project. It's the C library used by virtually all desktop and server GNU/Linux systems. It's feature-full, portable, complies to standards, but a bit bloated.
 * [http://en.wikipedia.org/wiki/Uclibc uClibc] is an alternate C library, which features a much smaller footprint. This library can be an interesting alternative if flash space and/or memory footprint is an issue. However, the space advantages gained using uClibc are becoming less important as the price of memory & flash continues to drop. There are a few "gotcha"s when using uClibc. At time of writing(uClibc 0.9.28), locales are a bit ropey and the new Application Binary Interface (ABI) for ARM architectures (EABI) introduced with GCC 4.1.1 requires patches to be applied. This situation is likely to get better quickly as uClibc is under heavy development.