From: Colin Helliwell <colin.helliwell@ln-systems.com>
To: yocto@yoctoproject.org,
Alexander Kanavin <alexander.kanavin@linux.intel.com>
Subject: Re: Slightly varying builds
Date: Thu, 2 Nov 2017 16:26:46 +0000 (GMT) [thread overview]
Message-ID: <1752415703.224739.1509640006960@email.1and1.co.uk> (raw)
In-Reply-To: <214703149.187142.1509606640635@email.1and1.co.uk>
> On 02 November 2017 at 07:10 Colin Helliwell <colin.helliwell@ln-systems.com> wrote:
>
> > On 01 November 2017 at 17:04 Alexander Kanavin <alexander.kanavin@linux.intel.com> wrote:
> >
> > On 11/01/2017 06:43 PM, colin.helliwell@ln-systems.com wrote:
> >
> > > I need to build two slightly varying versions of our Yocto build – one
> > > for the production units and one for development.
> > >
> > > They differ in only a few ways – the kernel and apps are the same. But
> > > one has Dropbear, whilst the other doesn’t; and the U-Boot configs &
> > > patches are different.
> > >
> > > I’m wondering where to do the separation – image, distro, conf…?
> > >
> > > Any thoughts on the cleanest way to split and/or inherit them would be
> > > appreciated.
> >
> > Image, certainly. Put the common bits into an include, and specific bits
> > into image-production|development.bb files. Poky has plenty of examples
> > for this.
>
> Rootfs changes I can certainly do with different image recipes.
>
> Am I right though in thinking that - because they'll have different variants of u-boot - I'll need to use separate build directories for each? (nb - I'm using signed FIT image, so the u-boot bin gets modified as part of the kernel building)
> --
Following on from this, I'm trying to be able to build my two versions of u-boot, in the *same* build directory.
I'm not sure if this is possible, but I figured it might be: since u-boot doesn't get put into the rootfs (?), I would ideally be able to build both and just pull down from tmp/deploy/images/.... the image that I want to program into a particular unit.
I've pushed common stuff into .inc file(s), and have two recipes which set different 'PROVIDES' values.
However, even after a cleanall on both recipes, bitbaking the second one throws an error "The recipe u-boot-mymachine-dev is trying to install files into a shared area when those files already exist".
Is it possible to do what I'm trying to do....?
Ta
next prev parent reply other threads:[~2017-11-02 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 16:43 Slightly varying builds colin.helliwell
2017-11-01 17:04 ` Alexander Kanavin
2017-11-02 7:10 ` Colin Helliwell
2017-11-02 16:26 ` Colin Helliwell [this message]
2017-11-02 16:29 ` Alexander Kanavin
2017-11-02 16:50 ` Colin Helliwell
2017-11-02 16:59 ` Alexander Kanavin
2017-11-02 17:22 ` Colin Helliwell
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=1752415703.224739.1509640006960@email.1and1.co.uk \
--to=colin.helliwell@ln-systems.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=yocto@yoctoproject.org \
/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.