From: Martin Jansa <martin.jansa@gmail.com>
To: Brad Litterell <brad@evidence.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Setting PV dynamically in a recipe
Date: Tue, 17 Dec 2013 15:01:59 +0100 [thread overview]
Message-ID: <20131217140159.GG3706@jama> (raw)
In-Reply-To: <E51394554A503C4E852F9BEE46B03E8D019AC4B3@TI-THOR.tasernet.com>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Tue, Dec 17, 2013 at 08:16:40AM +0000, Brad Litterell wrote:
> Hi,
>
> I have a few recipes in my image that represent my own custom code. I would like to generate PV dynamically from my source code, but since the recipe is parsed before the code is extracted from the tarball, that's not easy to do.
>
> The Poky reference manual implies this is possible:
> PV is generally not overridden within a recipe unless it is building an unstable (i.e. development) version from a source code repository (e.g. Git or Subversion).
>
> However, I have not found an actual example. Is there a recommended way to do this?
Do you really need to change PV? Check PKGV,
meta-openembedded/meta-oe/classes/gitpkgv.bbclass could be interesting
example for you.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-12-17 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 8:16 Setting PV dynamically in a recipe Brad Litterell
2013-12-17 9:41 ` zhenhua.luo
2013-12-17 19:46 ` Brad Litterell
2013-12-17 20:24 ` Paul Eggleton
2013-12-18 1:29 ` Brad Litterell
2013-12-18 9:36 ` Martin Jansa
2013-12-20 3:09 ` Brad Litterell
2013-12-20 9:34 ` Martin Jansa
2013-12-20 9:39 ` Brad Litterell
2013-12-20 10:01 ` Martin Jansa
2013-12-20 10:03 ` Brad Litterell
2013-12-20 10:11 ` Brad Litterell
2013-12-20 11:26 ` Martin Jansa
2013-12-17 14:01 ` Martin Jansa [this message]
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=20131217140159.GG3706@jama \
--to=martin.jansa@gmail.com \
--cc=brad@evidence.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.