[Buildroot] [PATCH] Added local package support.

Avishay Orpaz avishorp at gmail.com
Sun Jul 29 07:02:34 UTC 2012


Let me try to make my point with an example. Let's say I'm designing a
linux based digital camera. The software stack will probably include a
bunch of standard software component (kernel, busybox, flash utils etc.),
but there would also be at least one software component that is unique to
the design, and not intended to be shared with other designs - for example,
the GUI implementation of that specific model. This is the kind of software
I expect to see in the "local" directory. Of course this software component
can be put in the "package" directory, but I would think of buildroot as a
tool, which should not be modified and can be easily upgraded.

Regarding to the comment that other files in other directories may need to
be customized - it's very easy to put those files in any directory using
make variables according to one's project organization preference.

Committed or not, I really appreciate everyone's comments.


2012/7/27 Richard Braun <rbraun at sceen.net>

> On Fri, Jul 27, 2012 at 10:12:53AM +0200, Thomas Petazzoni wrote:
> > Le Fri, 27 Jul 2012 10:08:13 +0200,
> > Arnout Vandecappelle <arnout at mind.be> a écrit :
> > >   What do the others think?
> >
> > I am also a bit skeptical, but it's not yet a final and definitive
> > opinion. Custom packages is one thing, but one also very often need to
> > put stuff in board/ to keep kernel config, patches and various other
> > stuff, though it's true nothing prevent you to use $(TOPDIR)/../ to
> > keep track of all those things.
>
> I don't really see the point of the feature either. Keeping custom files
> in board and local packages in package/<company>/ is very easy to do and
> should suit most people fine. Local packages (those that use the local
> method) have one purpose : ease software development through the
> buildroot environment. I don't think people spend that much time on the
> .mk or Config.in files when using local packages. They spend time on
> the packaged software itself.
>
> --
> Richard Braun
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120729/f305f0e2/attachment-0002.html>


More information about the buildroot mailing list