Differences

This shows you the differences between two versions of the page.

about:toolchain [2013/07/03 15:46]
about:toolchain [2014/05/27 20:22] (current)
wutje old revision restored, previous had link spam
Line 5: Line 5:
A compilation toolchain is the set of tools used to compile code for your system. A compilation toolchain is the set of tools used to compile code for your system.
It consists of: It consists of:
-  * a compiler (in our case, ''[[wp>GNU Compiler Collection|gcc]]'' / [[http://packages.debian.org/squeeze/gcc|deb: gcc]]) +  * a compiler (in our case, ''[[wp>GNU Compiler Collection|gcc]]'' / [[http://packages.debian.org/wheezy/gcc|deb: gcc]]) 
-  * binary utils like assembler and linker (in our case, ''[[wp>GNU Binutils|binutils]]'' / [[http://packages.debian.org/squeeze/binutils|deb: binutils]] ) +  * binary utils like assembler and linker (in our case, ''[[wp>GNU Binutils|binutils]]'' / [[http://packages.debian.org/wheezy/binutils|deb: binutils]] )
  * a [[wp>C standard library]] (for example GNU Libc, uClibc or dietlibc).   * a [[wp>C standard library]] (for example GNU Libc, uClibc or dietlibc).
Line 56: Line 56:
  * Shipped „configure“ scripts are often faulty or unusable in a cross-compile setting, autoreconf or patching needed   * Shipped „configure“ scripts are often faulty or unusable in a cross-compile setting, autoreconf or patching needed
  * Build variants and kconfig includes allow for configurable compile-time settings   * Build variants and kconfig includes allow for configurable compile-time settings
-  * There is no standard way for porting software, in many cases it „just works“ but often the package build process needs +  * There is no standard way for porting software, in many cases it „just works“ but often the package build process needs tweaks
-  * tweaks+
===== Documentation ===== ===== Documentation =====

Back to top

about/toolchain.1372859175.txt.bz2 · Last modified: 2013/07/03 15:46 (external edit)