Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Felipe Ferreri Tonello <eu@felipetonello.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] protobuf: add protobuf-c recipe
Date: Wed, 20 Apr 2016 09:32:04 +0100	[thread overview]
Message-ID: <57173E84.90703@felipetonello.com> (raw)
In-Reply-To: <CADkTA4OyR2b_yCXFQ_NFzfEck_v3NvXGF4gUJLPGKcjvuHCFHA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3359 bytes --]

Hi Bruce,

On 19/04/16 20:55, Bruce Ashfield wrote:
> On Tue, Apr 19, 2016 at 3:46 PM, Bruce Ashfield <bruce.ashfield@gmail.com>
> wrote:
> 
>>
>>
>> On Tue, Apr 19, 2016 at 11:40 AM, Felipe F. Tonello <eu@felipetonello.com>
>> wrote:
>>
>>> Initial version of recipe. The main package could be split into two to
>>> separate the compiler. This also applies to protobuf recipe.
>>>
>>>
>> More precisely, this is the initial version outside of meta-virtualization
>> which enea added
>> in 2012 :) It was added as a dependency for criu (hence why it was put in
>> meta-virt).
>>
>> If we move it to meta-oe, we at least owe that other implementation a
>> reference in the commit.
>>
>>
> s/if/when/.
> 
> I'm happy to purge all the protobuf* recipes from meta-virt, since they
> were only there as
> support mechanisms (and I wasn't involved in their original merge).
> 
> But if you can take a look at what's in the meta-virt recipe, I'll do some
> runtime testing with your
> variant here, and drop the meta-virt ones when I can confirm criu works.
> 

Regular protobuf recipe is already part of meta-oe. That's why I added
this one there too.

> Cheers,
> 
> Bruce
> 
> 
>> Did you check the version we have there for deltas ? There are differences
>> in the recipe, and
>> it would be good to know if you've looked and determined they aren't
>> necessary.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>>> Signed-off-by: Felipe F. Tonello <eu@felipetonello.com>
>>> ---
>>>  .../recipes-devtools/protobuf/protobuf-c_1.2.1.bb  | 26
>>> ++++++++++++++++++++++
>>>  1 file changed, 26 insertions(+)
>>>  create mode 100644 meta-oe/recipes-devtools/protobuf/protobuf-c_1.2.1.bb
>>>
>>> diff --git a/meta-oe/recipes-devtools/protobuf/protobuf-c_1.2.1.bb
>>> b/meta-oe/recipes-devtools/protobuf/protobuf-c_1.2.1.bb
>>> new file mode 100644
>>> index 000000000000..88cdb0bccd8e
>>> --- /dev/null
>>> +++ b/meta-oe/recipes-devtools/protobuf/protobuf-c_1.2.1.bb
>>> @@ -0,0 +1,26 @@
>>> +SUMMARY = "Protocol Buffers - structured data serialisation mechanism"
>>> +DESCRIPTION = "This is protobuf-c, a C implementation of the Google
>>> Protocol Buffers data \
>>> +serialization format. It includes libprotobuf-c, a pure C library that \
>>> +implements protobuf encoding and decoding, and protoc-c, a code
>>> generator that \
>>> +converts Protocol Buffer .proto files to C descriptor code, based on the
>>> \
>>> +original protoc. protobuf-c formerly included an RPC implementation;
>>> that code \
>>> +has been split out into the protobuf-c-rpc project."
>>> +HOMEPAGE = "https://github.com/protobuf-c/protobuf-c"
>>> +SECTION = "console/tools"
>>> +LICENSE = "BSD-2-Clause"
>>> +
>>> +DEPENDS = "protobuf-native protobuf"
>>> +
>>> +PACKAGE_BEFORE_PN = "${PN}-compiler"
>>> +
>>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=235c3195a3968524dc1524b4ebea0c0e"
>>> +SRC_URI = "
>>> https://github.com/protobuf-c/protobuf-c/archive/v${PV}.tar.gz"
>>> +
>>> +SRC_URI[md5sum] = "b884aeba4283309445a8e3b6e7322dd6"
>>> +SRC_URI[sha256sum] =
>>> "2d708fb3c024b9e6e86df141faff802194f5db90a4b79e6d4aa6bd61dd983dd6"
>>> +
>>> +inherit autotools pkgconfig
>>> +
>>> +FILES_${PN}-compiler = "${bindir}"
>>> +
>>> +BBCLASSEXTEND = "native nativesdk"
>>> --
>>> 2.8.0
>>>
>>> --

Felipe

[-- Attachment #2: 0x92698E6A.asc --]
[-- Type: application/pgp-keys, Size: 7310 bytes --]

  reply	other threads:[~2016-04-20  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 15:40 [PATCH 0/2] Protobuf recipes update Felipe F. Tonello
2016-04-19 15:40 ` [PATCH 1/2] protobuf: add protobuf-c recipe Felipe F. Tonello
2016-04-19 19:46   ` Bruce Ashfield
2016-04-19 19:55     ` Bruce Ashfield
2016-04-20  8:32       ` Felipe Ferreri Tonello [this message]
2016-04-20 14:32         ` Bruce Ashfield
2016-04-28  8:02           ` Felipe Ferreri Tonello
2016-04-28 13:16             ` Bruce Ashfield
2016-04-19 15:40 ` [PATCH 2/2] protobuf: Split package to main and compiler packages Felipe F. Tonello
  -- strict thread matches above, loose matches on Subject: below --
2016-05-03 15:20 [PATCH 0/2] Protobuf recipes update Felipe F. Tonello
2016-05-03 15:20 ` [PATCH 1/2] protobuf: add protobuf-c recipe Felipe F. Tonello

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=57173E84.90703@felipetonello.com \
    --to=eu@felipetonello.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox