Re: [yocto] Yocto and Google protobuffer

2016-09-06 20:11 GMT+02:00 Khem Raj : > >> On Sep 1, 2016, at 3:57 AM, Samuel Stirtzel >> wrote: >> >> Hi, >> >> protobuf 2.x and 3.x are incompatible, there is also a protobuf3 >> recipe in meta-maker. >> > > why is it in meta-maker and not in

Re: [yocto] Yocto and Google protobuffer

> On Sep 1, 2016, at 3:57 AM, Samuel Stirtzel wrote: > > 2016-09-01 12:34 GMT+02:00 Jussi Kukkonen : >> On 1 September 2016 at 13:21, Herman van Hazendonk wrote: >>> >>> Hi Pietro, >>> >>> You can override the recipe by

Re: [yocto] Yocto and Google protobuffer

Maciej Borzęcki writes: > On Thu, Sep 1, 2016 at 5:45 PM, Pietro wrote: >> Herman van Hazendonk >> writes: >> >>> If it takes the wrong version, it could be your layers aren't in the >>> right order. That's the first thing

Re: [yocto] Yocto and Google protobuffer

On Fri, Sep 2, 2016 at 10:08 AM, Pietro wrote: > Maciej Borzęcki > writes: > >> On Thu, Sep 1, 2016 at 5:45 PM, Pietro wrote: >>> Herman van Hazendonk >>> writes: >>> If it takes the wrong

Re: [yocto] Yocto and Google protobuffer

Maciej Borzęcki writes: > On Thu, Sep 1, 2016 at 5:45 PM, Pietro wrote: >> Herman van Hazendonk >> writes: >> >>> If it takes the wrong version, it could be your layers aren't in the >>> right order. That's the first thing

Re: [yocto] Yocto and Google protobuffer

On Thu, Sep 1, 2016 at 5:45 PM, Pietro wrote: > Herman van Hazendonk > writes: > >> If it takes the wrong version, it could be your layers aren't in the >> right order. That's the first thing to check. >> >> You might want to try to run bitbake with >>

Re: [yocto] Yocto and Google protobuffer

Herman van Hazendonk writes: > If it takes the wrong version, it could be your layers aren't in the > right order. That's the first thing to check. > > You might want to try to run bitbake with > > -f protobuf -c cleanall or -f protobuf-native -c cleanall > > This will remove

Re: [yocto] Yocto and Google protobuffer

If it takes the wrong version, it could be your layers aren't in the right order. That's the first thing to check. You might want to try to run bitbake with -f protobuf -c cleanall or -f protobuf-native -c cleanall This will remove all locally ;) Then rebuild it... I haven't played much with

Re: [yocto] Yocto and Google protobuffer

Herman van Hazendonk writes: > Hi Pietro, > > You shouldn't need to specify a version. DEPENDS = "protobuf" or > DEPENDS = "protobuf-native" should do :) > > Herrie > > > Indeed my recipe gets built first and I can see do_protobuf_3.0.0[..](), nonetheless when my package, which

Re: [yocto] Yocto and Google protobuffer

Hi Pietro, You shouldn't need to specify a version. DEPENDS = "protobuf" or DEPENDS = "protobuf-native" should do :) Herrie On 2016-09-01 15:40, Pietro wrote: Pietro writes: Jussi Kukkonen writes: On 1 September 2016 at 13:21,

Re: [yocto] Yocto and Google protobuffer

Pietro writes: > Jussi Kukkonen > writes: > >> On 1 September 2016 at 13:21, Herman van Hazendonk >> wrote: >> >> Hi Pietro, >> >> You can override the recipe by adding a recipe for version 3.0.0+ >> in your

Re: [yocto] Yocto and Google protobuffer

Jussi Kukkonen writes: > On 1 September 2016 at 13:21, Herman van Hazendonk > 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

Re: [yocto] Yocto and Google protobuffer

2016-09-01 12:34 GMT+02:00 Jussi Kukkonen : > On 1 September 2016 at 13:21, Herman van Hazendonk 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

Re: [yocto] Yocto and Google protobuffer

On 1 September 2016 at 12:34, Pietro wrote: > Maciej Borzęcki > writes: > > > On Thu, Sep 1, 2016 at 10:40 AM, Pietro wrote: > >> Maciej Borzęcki > >> writes: > >> > >>> On Wed, Aug 31,

Re: [yocto] Yocto and Google protobuffer

On 1 September 2016 at 13:21, Herman van Hazendonk 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: > >

Re: [yocto] Yocto and Google protobuffer

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

Re: [yocto] Yocto and Google protobuffer

Maciej Borzęcki writes: > On Thu, Sep 1, 2016 at 10:40 AM, Pietro wrote: >> Maciej Borzęcki >> writes: >> >>> On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote: Hi all, I am

Re: [yocto] Yocto and Google protobuffer

On Thu, Sep 1, 2016 at 10:40 AM, Pietro wrote: > Maciej Borzęcki > writes: > >> On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote: >>> Hi all, >>> >>> I am new to the Yocto building system and I could be talking nonsense.

Re: [yocto] Yocto and Google protobuffer

Maciej Borzęcki writes: > On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote: >> Hi all, >> >> I am new to the Yocto building system and I could be talking nonsense. I >> used to work with buildroot time ago and I remember there is an area >>

Re: [yocto] Yocto and Google protobuffer

On Wed, Aug 31, 2016 at 6:44 PM, Pietro wrote: > Hi all, > > I am new to the Yocto building system and I could be talking nonsense. I > used to work with buildroot time ago and I remember there is an area > where compiled software/packages/tools previously built are

[yocto] Yocto and Google protobuffer

Hi all, I am new to the Yocto building system and I could be talking nonsense. I used to work with buildroot time ago and I remember there is an area where compiled software/packages/tools previously built are "staged" and used when building other packages. Is there something like that available