[Buildroot] [v3, 1/4] barebox: prepare for secondary config build
Pieter Smith
pieter at boesman.nl
Sun Feb 28 08:12:04 UTC 2016
On Sat, Feb 27, 2016 at 12:17:15AM +0100, Arnout Vandecappelle wrote:
> On 01/20/16 23:43, Pieter Smith wrote:
[snip]
> I wonder if it wouldn't be possible to keep barebox.mk unchanged, and just add
> at the end (after the kconfig-package):
>
> include boot/barebox/barebox-2/barebox-2.mk
>
> That's not entirely similar to gcc, but it's more consistent with what it
> means. You always have the barebox package, and you have an optional extra
> barebox-2 package which is a kind of submodule of barebox. Note however that we
> currently don't have this pattern at all, so it could be controversial. But I
> think it will simplify the patch a lot, and also simplify the logic.
>
> So in that case, you'd have a first patch that adds the required refactorings
> in barebox.mk so the same variables are useable for barebox-2, and a second
> patch that adds barebox-2 (and patches 3 and 4 stay the same of course).
Yes. Thanks. A lot less messy. I started looking into this. It seems doable. It
might be neater to still split a barebox-common.mk to avoid a long list of
variable copies. Give me a day on this.
> This is complicated stuff, thanks for working on this, and sorry that it's
> taking so long!
>
> Regards,
> Arnout
>
> [snip]
>
> --
> Arnout Vandecappelle arnout at mind be
> Senior Embedded Software Architect +32-16-286500
> Essensium/Mind http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
- Pieter
More information about the buildroot
mailing list