All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 1/2] protobuf: add protobuf-c recipe
Date: Tue, 19 Apr 2016 15:46:09 -0400	[thread overview]
Message-ID: <CADkTA4Pi3dG1G4DZ+rNEfwVnMJZxDNBfXtXv_fMKprkgBmRquQ@mail.gmail.com> (raw)
In-Reply-To: <1461080418-9229-2-git-send-email-eu@felipetonello.com>

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.

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
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"


  reply	other threads:[~2016-04-19 19:46 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 [this message]
2016-04-19 19:55     ` Bruce Ashfield
2016-04-20  8:32       ` Felipe Ferreri Tonello
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
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=CADkTA4Pi3dG1G4DZ+rNEfwVnMJZxDNBfXtXv_fMKprkgBmRquQ@mail.gmail.com \
    --to=bruce.ashfield@gmail.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 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.