From: Pietro <pulsarpietro@posteo.net>
To: yocto@yoctoproject.org
Subject: Re: Yocto and Google protobuffer
Date: Thu, 01 Sep 2016 13:10:55 +0000 [thread overview]
Message-ID: <87bn07bw9s.fsf@posteo.net> (raw)
In-Reply-To: CAHiDW_GBefiLcDQOgEEPVXeKTQGun8w6n62H33V6W4bvCv6sSA@mail.gmail.com
Jussi Kukkonen <jussi.kukkonen@intel.com>
writes:
> 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/testing/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
Thanks a lot.
I have written my own repice and added it into my own layer, it
does not compile though :
|
| autoreconf: configure.ac: tracing
|
| autoreconf: configure.ac: subdirectory gmock not present
| autoreconf: configure.ac: not using Libtool
| autoreconf: running:
| /export/arm/pietro/PD15.1/build/tmp-glibc/sysroots/x86_64-linux/usr/bin/autoconf
| --include=/export/arm/pietro/PD15.1/build/tmp-glibc/work/cortexa8t2hf-vfp-neon-phytec-linux-gnueabi/proto
buf/3.0.0-r0/git/m4/ --force
|
| configure.ac:93: error: possibly undefined macro: AC_PROG_LIBTOOL
|
| If this token and others are legitimate, please use
| m4_pattern_allow.
| See the Autoconf documentation.
|
| autoreconf:
| /export/arm/pietro/PD15.1/build/tmp-glibc/sysroots/x86_64-linux/usr/bin/autoconf
| failed with exit status: 1
|
| + bbfatal autoreconf execution failed.
I understand this is a completely different matter now, but has
anybody else seen this before ? I have tried to compile the same
revision on my local machine "natively" and it's built fine.
That library should be a dependency for another package/recipe I am
working on, is it allowed to specify a version inside the DEPENDS
recipe's clause ? I have tried to google the problem but I haven't found
a working example as yet.
Cheers,
P.
next prev parent reply other threads:[~2016-09-01 13:10 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
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 [this message]
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=87bn07bw9s.fsf@posteo.net \
--to=pulsarpietro@posteo.net \
--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.