This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: crosstool vs. building from scratch



On 9-Feb-06, at 2:07 PM, Trevor Harmon wrote:


I am reading Karim Yaghmour's book, "Building Embedded Linux Systems," and in Chapter 4 he goes into great detail about building a cross-compiling GCC toolchain from scratch. He describes how to download and compile GCC, binutils, and kernel headers in separate steps.

In the same year of the book's publication, a set of scripts and templates called crosstool [1] was released. It automates the entire process of Yaghmour's Chapter 4 down to a single command (more or less). I have used crosstool successfully for building PowerPC executables on an x86 host.

Because I'm new to cross-compiling, I'm curious about the differences between these two techniques. I've never tried the from- scratch method, but my assumption is that as long as crosstool can build the toolchain successfully, then there's no reason to do anything from scratch.

Is this assumption correct, or are there developers who can use crosstool but still prefer the from-scratch method (for more flexibility, for instance)? In other words, if crosstool is working for me, is there any situation where I would still want to build the toolchain from scratch?

Unless you want to learn something about how a toolchain is put together, just use crosstool. I started with scratch-built tool chains, then switched to crosstool because I've got better things to do with my time.


g.


------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.org


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]