From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] avahi dependencies on host tools
Date: Wed, 16 Dec 2009 15:47:56 +0100 [thread overview]
Message-ID: <20091216154756.7e5b3db2@surf> (raw)
In-Reply-To: <5f2b60912160550x6d3ae47eu4f625f0259737e95@mail.gmail.com>
Le Wed, 16 Dec 2009 14:50:26 +0100,
Bj?rn Forsman <bjorn.forsman@gmail.com> a ?crit :
> IMHO, I'd like for Buildroot to build the least amount of host tools
> so that build times can be kept down. I often start from
> scratch... :-)
True, but on the other hand, the approach we've been following since
Buildroot maintenance has been taken over by Peter is that we should
only rely on "basic" tools on the host. That's the reason why we build
autoconf, automake, glib, pkg-config and other stuff for the host as
needed. It makes the compilation process a little longer, but on the
other hand, it makes the build process a *lot* more predictable.
In the past, we had tons of reports of build failures that were caused
by issues in varying versions of the host tools. And these problems are
particularly annoying since the Buildroot developers often can't
reproduce them.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-12-16 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 9:24 [Buildroot] avahi dependencies on host tools Thomas Petazzoni
2009-12-16 13:50 ` Bjørn Forsman
2009-12-16 14:47 ` Thomas Petazzoni [this message]
2009-12-16 17:15 ` Bjørn Forsman
2009-12-16 17:29 ` Sven Neumann
2009-12-16 19:26 ` Peter Korsgaard
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=20091216154756.7e5b3db2@surf \
--to=thomas.petazzoni@free-electrons.com \
--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