[Buildroot] Documentation question

[Michael S. Zick]

On Wed December 9 2009, Grant Edwards wrote:
> I've been reading the "buildroot usage and documentation"
> document over the past couple days, and in order to not be a
> complete leech, I'm fixing various minor problems (typos,
> spelling, punctuation, usage, grammar, etc.) and will submmit a
> patch when I've finished.
> 
> However, I've run across one paragraph where I think the actual
> content could use a tweak, and I thought I should ask about it
> before making a change.  In the section "Using Buildroot"
> there's a paragraph that describes what the top-level "make"
> does:
> 
>    $ make
> 
>      This command will download, configure and compile all the
>      selected tools, and finally generate a toolchain, a root
>      filesystem image and a kernel image (or only one of these
>      elements, depending on the configuration). 
> 
> Doesn't the toolchain have to be generated _before_ the
> selected tools are configured and compiled?
> 

Just needs some clarification.

"Generate toolchain" in the sentence seems to mean a native
toolchain (which Buildroot can do - similar to any other package).

What you are referring too seems to be an cross-compile toolchain.
Which does not seem to be mentioned (or maybe the native toolchain isn't mentioned).

*) Downloads (either as required, or pre-downloads all (make source))
*) Configures cross-compile toolchain
*) Builds cross-compile toolchain
*) Builds selected packages (optional)
*) Builds a native toolchain (optional, like any other "package")
*) Builds a kernel image (optional)
*) Creates a root filesystem in selectable forms (filesystem, archive, ...)

Or something close to that - notice two (2) "toolchains"

Mike
> IOW, "generate a toolchain" seems to me to be in the wrong
> place in the sequence.  Right?
>