From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Colin Helliwell <colin.helliwell@ln-systems.com>, yocto@yoctoproject.org
Subject: Re: Slightly varying builds
Date: Thu, 2 Nov 2017 18:29:43 +0200 [thread overview]
Message-ID: <872a75ce-9471-09fb-e00d-0ae5da82634a@linux.intel.com> (raw)
In-Reply-To: <1752415703.224739.1509640006960@email.1and1.co.uk>
On 11/02/2017 06:26 PM, Colin Helliwell wrote:
> 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".
Can you share exactly how the two recipes differ?
It seems that you do need to have two different build directories that
differ in what MACHINE is set to. And that would configure u-boot
accordingly.
Alex
next prev parent reply other threads:[~2017-11-02 16:29 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
2017-11-02 16:29 ` Alexander Kanavin [this message]
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=872a75ce-9471-09fb-e00d-0ae5da82634a@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=colin.helliwell@ln-systems.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.