Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Documentation question
Date: Wed, 9 Dec 2009 16:32:03 -0600	[thread overview]
Message-ID: <200912091632.06109.minimod@morethan.org> (raw)
In-Reply-To: <hfp1uh$6fk$1@ger.gmane.org>

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?
> 

  parent reply	other threads:[~2009-12-09 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 20:39 [Buildroot] Documentation question Grant Edwards
2009-12-09 21:11 ` Grant Edwards
2009-12-09 22:32 ` Michael S. Zick [this message]
2009-12-09 22:54   ` Grant Edwards
2009-12-09 23:07     ` Michael S. Zick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200912091632.06109.minimod@morethan.org \
    --to=minimod@morethan.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox