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: Fri, 02 Sep 2016 08:08:22 +0000	[thread overview]
Message-ID: <87oa46afm1.fsf@posteo.net> (raw)
In-Reply-To: CAD4b0_KE4c3EFan96E7FzaNofJgB7mYjD3VDV=Wr4MwD0fXC-A@mail.gmail.com

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

> On Thu, Sep 1, 2016 at 5:45 PM, Pietro <pulsarpietro@posteo.net> wrote:
>> Herman van Hazendonk <me@herrie.org>
>> 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 all locally ;)
>>>
>>> Then rebuild it... I haven't played much with the -native bits, so not
>>> sure how those work.
>>>
>> I needed to specify DEPENDS = "protobuf-native" to get it working, I
>> would be really interested to understand exactly what that does, but I
>> must admit to myself I can't understand everything in a single shot.
>
> Quoting my first email:
>>> 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.
>
> DEPENDS lists build time dependencies, like libraries, tools etc.
> protobuf-native, by convention, means that the package was built for
> your build host. This enables you to run protoc during the build to
> generate proper language bindings.
>
Where are all these "native" binaries stored ? Is it "sysroot" ?

How can I declare run-time dependencies ?

Such library should be cross-compiled in order to successfully
link my package's binaries against it, on the other hand when building
the "protoc" the target should be the host machine as such tool will be
run on the host machine when required.

I wonder if is the "native" keyword in the DEPENDS statement to draw the
line, so in a recipe A:

i) DEPENDS = "protobuf"
   tells that the recipe depends on the protobuf at run-time - namely during
   the linking and when the binary resulting from A is executed.
   So protobuf is cross-compiled.
   
ii) DEPENDS = "protobuf-native"
    tells that the recipe depends on the prottobuf at build-time and a
    result of that protobuf is NOT cross compiled.

>>
>> So never mind.
>>
>> I still have another question :-)
>>
>> I am about to create another recipe for the gprc library for C++, to
>> build it on my local machine has been pretty simple:
>>
>> $ git clone -b $(curl -L http://grpc.io/release)
>> https://github.com/grpc/grpc
>> $ cd grpc
>> $ git submodule update --init
>> $ make
>> $ [sudo] make install
>>
>> The recipe I have created so far would clone/checkout the source code
>> from a GIT repo or something similar and then the build process could
>> start straight away.
>>
>> In my case I have an additional step:
>>
>> git submodule update --init
>>
>
> There's a submodule fetcher, when setting SRC_URI use `gitsm://`
> instead of `git://` see
> https://www.yoctoproject.org/docs/2.1/bitbake-user-manual/bitbake-user-manual.html#gitsm-fetcher
> for details.
>
> Cheers,
> -- 
> Maciej Borzecki
> RnDity
Thanks, I'll give to it a go.



  reply	other threads:[~2016-09-02  8:08 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
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 [this message]
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=87oa46afm1.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.