Re: Building Kernel w/ crosstool

[Daniel Kegel <dank at kegel dot com>]

Royce Kemp wrote:
> embedded developer/crosstool newbie here who just successfully built a 
> toolchain. wow that was easy! thank you dan kegel!

You're welcome.

> now my next step is to build myself a kernel, but I was unclear how best 
> to proceed: do i want to build the kernel using the source that was 
> untarred into the build directory? or was that just to produce the 
> kernel headers for building the toolchain? and if that's the case, then 
> I don't really need to customize the .config file (i686.config in my 
> case) as that was just to run make config. right? i hope that's right 
> b/c then applying kernel patches (i.e. netfilters) can be deferred until 
> after the toolchain is built.

Right.  The kernel source in crosstool is only for headers.
(Well, and for the regression test; I check to make sure I can build it
sometimes.)  In fact, you can even build crosstool without
the kernel source, if you use the 'sanitized kernel headers' option.
(I'm just trying that out myself, so it's not documented yet,
but grep for SANITIZED if you want to try it.)

> i really like crosstool's idea of decoupling the 'creation of 
> toolchains' from the 'usage of toolchains'. i had adopted the format 
> used by Karim Yaghmour in Building Embedded Linux Systems which seemed 
> to couple the embedded project with the toolchain itself. it was my 
> desire to escape that constraint which led me to Google, which led me to 
> crosstool. :)

Well, Karim's a smart guy.  He's right that projects need to
use a particular toolchain if they want to be stable.
But there's nothing saying that toolchain can't be generated
by crosstool.
- Dan

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