[Buildroot] User-enabled host packages?

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Sep 21 13:31:33 UTC 2011

Le Wed, 21 Sep 2011 15:00:49 +0200,
Luca Ceresoli <luca at 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 ?


Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.

More information about the buildroot mailing list