From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] User-enabled host packages?
Date: Wed, 21 Sep 2011 15:31:33 +0200 [thread overview]
Message-ID: <20110921153133.2d816865@skate> (raw)
In-Reply-To: <4E79E001.7010409@lucaceresoli.net>
Le Wed, 21 Sep 2011 15:00:49 +0200,
Luca Ceresoli <luca@lucaceresoli.net> a ?crit :
> All of these examples are about tools that could generally be
> downloaded, built and installed by each developer on their own
> machine. Nevertheless any developer may benefit from having them
> built inside buildroot: it would be more handy and quick to build
> them, and also guarantee that the version used in buildroot is
> somehow tested by other buildroot users.
>
> Moreover, some packages (such as omap-u-boot-utils for which I posted
> a patch) have their own right of being inside buildroot because they
> also contribute to building the BR images. Having a user option to
> build them, even if they are not required for image generation, would
> require little effort.
>
> So the big question is: do we want some host packages to be enabled
> vie a user option?
>
> Where do we want these user options?
> How about a newly created "Host tools" menu at top level?
>
> Does anybody have additional examples in favor or against?
And also:
If we decide to show /some/ host tools (but not all) in menuconfig, what
is the boundary between host tools visible in menuconfig and those not
visible in menuconfig ?
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-21 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 13:00 [Buildroot] User-enabled host packages? Luca Ceresoli
2011-09-21 13:31 ` Thomas Petazzoni [this message]
2011-09-22 20:15 ` Luca Ceresoli
2011-09-22 20:53 ` Arnout Vandecappelle
2011-09-23 7:46 ` Thomas Petazzoni
2011-09-30 12:50 ` Thomas De Schampheleire
2011-09-30 13:50 ` Arnout Vandecappelle
2011-09-30 14:04 ` Thomas Petazzoni
2011-09-30 16:46 ` Thomas De Schampheleire
2011-09-30 17:58 ` Thomas Petazzoni
2011-09-30 18:29 ` Thomas De Schampheleire
2011-09-30 21:57 ` Luca Ceresoli
2011-10-01 20:11 ` Arnout Vandecappelle
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=20110921153133.2d816865@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.