From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: yoctoproject.org@herrie.org
Cc: Yocto Project <yocto@yoctoproject.org>, Pietro <pulsarpietro@posteo.net>
Subject: Re: Yocto and Google protobuffer
Date: Thu, 1 Sep 2016 13:34:15 +0300 [thread overview]
Message-ID: <CAHiDW_GBefiLcDQOgEEPVXeKTQGun8w6n62H33V6W4bvCv6sSA@mail.gmail.com> (raw)
In-Reply-To: <85bd928a2ecb47663d9a90ca24756f16@herrie.org>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On 1 September 2016 at 13:21, Herman van Hazendonk <me@herrie.org> wrote:
> Hi Pietro,
>
> You can override the recipe by adding a recipe for version 3.0.0+ in your
> own layer and making sure your layer has a higher priority in
> bblayers.conf. See for example what we do in our project:
>
> https://github.com/webOS-ports/webos-ports-setup/blob/testin
> g/conf/bblayers.conf
>
> openembedded-core provides ofono 1.1.7 for example with
> https://github.com/openembedded/openembedded-core/tree/
> krogoth/meta/recipes-connectivity/ofono
>
> However we want to use ANOTHER version of ofono (1.1.7 based, but from a
> different repo/project).
>
> So we have our own .bbappend at https://github.com/webOS-ports
> /meta-webos-ports/blob/krogoth/meta-luneos/recipes-connectiv
> ity/ofono/ofono_git.bbappend where we specify the different repo etc to
> use.
>
> This doesn't apply 1:1 in your case, but you could simply add a
> protobuf_3.0.0.bb in your own layer and it should build that instead.
> Just make sure you have your layer at a higher position compared to
> meta-openembedded in your bblayers.conf
>
In the normal case (a simple upgrade to the newest version) the best choice
would be to send a upgrade patch to openembedded-devel list: that way you
never have to maintain it in your own layer.
Jussi
[-- Attachment #2: Type: text/html, Size: 2278 bytes --]
next prev parent reply other threads:[~2016-09-01 10:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 16:44 Yocto and Google protobuffer Pietro
2016-09-01 7:50 ` Maciej Borzęcki
2016-09-01 8:40 ` Pietro
2016-09-01 9:02 ` Maciej Borzęcki
2016-09-01 9:34 ` Pietro
2016-09-01 10:21 ` Herman van Hazendonk
2016-09-01 10:34 ` Jussi Kukkonen [this message]
2016-09-01 10:57 ` Samuel Stirtzel
2016-09-06 18:11 ` Khem Raj
2016-09-08 12:42 ` Samuel Stirtzel
2016-09-01 13:10 ` Pietro
2016-09-01 13:40 ` Pietro
2016-09-01 13:44 ` Herman van Hazendonk
2016-09-01 14:34 ` Pietro
2016-09-01 14:40 ` Herman van Hazendonk
2016-09-01 15:45 ` Pietro
2016-09-01 15:56 ` Maciej Borzęcki
2016-09-02 8:08 ` Pietro
2016-09-02 8:37 ` Maciej Borzęcki
2016-09-02 9:44 ` Pietro
2016-09-01 10:43 ` Jussi Kukkonen
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=CAHiDW_GBefiLcDQOgEEPVXeKTQGun8w6n62H33V6W4bvCv6sSA@mail.gmail.com \
--to=jussi.kukkonen@intel.com \
--cc=pulsarpietro@posteo.net \
--cc=yocto@yoctoproject.org \
--cc=yoctoproject.org@herrie.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.