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:59:36 +0200 [thread overview]
Message-ID: <9857d70a-0429-6777-d29d-e797cbd9bdd4@linux.intel.com> (raw)
In-Reply-To: <198351249.226064.1509641440918@email.1and1.co.uk>
On 11/02/2017 06:50 PM, Colin Helliwell wrote:
>
> u-boot-w2_1.inc has the standard kind of recipe stuff. For creating env files, and files to be used for later signing, it has some _append steps, so I'm aiming to use 'DEP_IMG' to create the various files with different prefixes for the two variants.
> Strangely though, an 'echo ${DEP_IMG}' is outputting the same value ("u-boot-prodn") from both recipes, even after a cleanall on both. Possibly some state info being pulled in somewhere?
Not sure if this will help, but start by not using the -dev suffix. It
will clash with -dev packages produced by (any) recipe.
Alex
next prev parent reply other threads:[~2017-11-02 16:59 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
2017-11-02 16:50 ` Colin Helliwell
2017-11-02 16:59 ` Alexander Kanavin [this message]
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=9857d70a-0429-6777-d29d-e797cbd9bdd4@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.