From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
Date: Fri, 26 Sep 2014 13:56:24 +0200 (CEST)
Subject: [Buildroot] Raspaudio : how to use buildroot as a git submodule
In-Reply-To: <CAM+bi4sfYENe4DM8vDvEen+kSKqQWyyEAReD8NKX9gnHMArjgA@mail.gmail.com>
Message-ID: <2070245131.25765734.1411732584201.JavaMail.root@openwide.fr>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net


> Hi, Jeremy, all
> 
> I've been testing this for a few days and I've come to love it :)
> 
> For now, I've just found a problem.
> 
> I've tried to replace buildroot's default package definition for
> libconfuse with my own (it's just a version bump),
> but since I don't want to touch buildroot's master branch, I've added
> a copy of package/libconfuse to the $BR2_EXTERNAL directory,
> alongisde
> custom Config.in and external.mk
> 
> This, however, results in duplicated definitions, and although make
> tries to solve it by overriding previously declared definitions with
> the new ones, there are some conflicts:
> 
> 

...

> 
> As can be seen, the patch is being applied to libconfuse-V2_7, which
> is buildroot's declared version of libconfuse, while it should have
> been applied to master version as I declared on the outside
> buildroot's directory external makefile.
> 
> For now, I'll have to maintain a different buildroot branch in which
> this package is modified, since I've not being able to override
> buildroot's definition.
> 

That's an incencitive to upstream, no ? :P

more seriously, if you want to do that, I would recommand 
* either renaming the package entirely. 
* or use the OVERRRIDE_SRC_DIR macro (see usermanual)

> All in all, however, I'm very happy with the environment your
> Makefile
> provides. I've done a couple changes that I hope will publish in the
> following week for comments.
> 

please do, I'll happily integrate... At this stage the framework satisfies all my needs so I need external ideas to make it live :)

> Kind regards,
> 
> 
> 2014-03-10 16:38 GMT+01:00 Jeremy Rosen <jeremy.rosen@openwide.fr>:
> >
> >
> >>
> >>
> >> Hi, Jeremy
> >>
> >> Personally, I see potential in this.
> >>
> >> Have you thought of a way to include custom packages outside the
> >> buildroot hierarchy?
> >>
> >>
> >> Just as an example to illustrate the question, in the case of
> >> NOOBS
> >> ( https://github.com/raspberrypi/noobs ), maybe the NOOBS
> >> application
> >> (
> >> https://github.com/raspberrypi/noobs/blob/master/buildroot/package/recovery/recovery.mk
> >> )
> >> itself isn't well suited for buildroot upstream for it's very
> >> architecure dependent.
> >>
> >
> >
> > yes, this is exactly what I wanted to avoid, a project that has to
> > include all of buildroot in a subdirectory and thus has problems
> > following upstream.
> >
> > You can include external software in the raspaudio infrastructre
> > because
> > this infrastucture relies on the BR2_EXTERNAL feature of buildroot
> > that allows external software to be built.
> >
> > You just need to include your own software via the external.mk and
> > Config.in files that are at the root of raspaudio-based project.
> >
> > I need to test and document that properly, but it works
> >
> >
> >>
> >> So, have you thought of some way to place this directory outside
> >> buildroots hierarchy but
> >> let it be managed by buildroot? That, alongside your scripts and
> >> makefiles would allow
> >> to create root file systems with custom packages without
> >> "polluting"
> >> the buildroot
> >> directory/repository.
> >>
> >
> >
> > That's exactly the point of raspaudio. Feel free to test and report
> > any
> > problem you have. I have been the only one testing it so far and I
> > might have missed some important stuff..
> >
> >
> > Boucman
> 
> 
> 
> --
> ?lvaro G?mez Machado
>