All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pietro <pulsarpietro@posteo.net>
To: yocto@yoctoproject.org
Subject: Re: Yocto and Google protobuffer
Date: Thu, 01 Sep 2016 08:40:32 +0000	[thread overview]
Message-ID: <87k2ewau7z.fsf@posteo.net> (raw)
In-Reply-To: CAD4b0_JqqWmkL5egXgbSVvq5xpb-ck2-sj9rr3hBbcOeEB5-VQ@mail.gmail.com

Maciej Borzęcki
<maciej.borzecki@rndity.com> writes:

> On Wed, Aug 31, 2016 at 6:44 PM, Pietro <pulsarpietro@posteo.net> 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 "staged" and
>> used when building other packages.
>>
>> Is there something like that available with Yocto ? Specifically I would
>> like to add a package which uses the Google Protocol Buffer, I do not have
>> administrator rights on the machine and I can't install the packages I
>> need system wise.
>>
>> Is it possible to add recipes and use them at building time without
>> including them in the image being generated ?
>>
>> A good example for that would be the protoc, the protocol buffer description
>> file compiler.
>>
>
> There is a recipe for protobuf in meta-oe (2.6.1). All you need to do,
> is include meta-oe in your layers (bblayers.conf) and have
> protobuf-native listed in DEPENDS inside your package recipe.
>
> The protoc compiler will be available in the PATH when package is
> being built, so autotools checks like AC_CHECK_PROG/AC_PATH_PROG
> should be able to find it.
>
> Cheers,
> -- 
> Maciej Borzecki
> RnDity
Thanks a lot.

I have added the DEPENDS line and it indeed downloads and build the some
protobuf related stuff, where did you get the dependency name from ?
I can't see the protobuf-native as a recipe in the meta-oe website :

https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/

I have just realised that GRPC (http://www.grpc.io/) is needed for my
project, it is a library which uses the protobuffers, is there a
recipe/package which provides them around or do I need to create my own
recipe ?

I would like to check the root filesystem being generated as part of the
build process, where is it ?




  reply	other threads:[~2016-09-01  8:40 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 [this message]
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
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=87k2ewau7z.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.