Differences
This shows you the differences between two versions of the page.
|
about:toolchain [2012/12/17 23:29] uvray313 |
about:toolchain [2012/12/17 23:30] (current) uvray313 |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| As said above, the compilation toolchain that comes with your system runs and generates code for the processor of your host system. As your embedded system has a different processor, you need a cross-compilation toolchain: it's a compilation toolchain that runs on your host system but that generates code for your target system (and target [[doc:hardware:cpu|processor]]'s ISA). For example, if your host system uses x86 and your target system uses MIPS32, the regular compilation toolchain of your host runs on x86 and generates code for x86, while the cross-compilation toolchain runs on x86 and generates code for MIPS32. | As said above, the compilation toolchain that comes with your system runs and generates code for the processor of your host system. As your embedded system has a different processor, you need a cross-compilation toolchain: it's a compilation toolchain that runs on your host system but that generates code for your target system (and target [[doc:hardware:cpu|processor]]'s ISA). For example, if your host system uses x86 and your target system uses MIPS32, the regular compilation toolchain of your host runs on x86 and generates code for x86, while the cross-compilation toolchain runs on x86 and generates code for MIPS32. | ||
| - | You might wonder why such a tool is needed when you can compile [[wp>GNU Compiler Collection|gcc]], [[wp>GNU_Binutils|binutils]], ''uClibc'' and all the tools by hand. Well, it is not needed. Of course, you can do everything manually, but dealing with all the configure options, with all problems of every ''gcc'' or ''binutils'' version is very time-consuming and uninteresting. OpenWrt Buildroot automates this process through the use of Makefiles, and has a collection of patches for each ''gcc'' and ''binutils'' version to make them work on the respective instruction set architecture of most embedded systems. | + | You might wonder why such a tool is needed when you can compile ''gcc'', ''binutils'', ''uClibc'' and all the tools by hand. Well, it is not needed. Of course, you can do everything manually, but dealing with all the configure options, with all problems of every ''gcc'' or ''binutils'' version is very time-consuming and uninteresting. OpenWrt Buildroot automates this process through the use of Makefiles, and has a collection of patches for each ''gcc'' and ''binutils'' version to make them work on the respective instruction set architecture of most embedded systems. |
| While the OpenWrt Buildroot was intended mostly for developers, it is still simple enough that an inexperienced end user can easily build his or her own customized firmware! | While the OpenWrt Buildroot was intended mostly for developers, it is still simple enough that an inexperienced end user can easily build his or her own customized firmware! | ||
about/toolchain.txt · Last modified: 2012/12/17 23:30 by uvray313