From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Samuel Stirtzel" <s.stirtzel@googlemail.com>,
"David Nyström" <david.nystrom@enea.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 1/3] protobuf: add recipe from meta-virtualization and tweak
Date: Tue, 16 Jul 2013 18:07:01 +0100 [thread overview]
Message-ID: <2169768.F21dFWYplB@helios> (raw)
In-Reply-To: <CAGiJk9cSOsY4Lb1-KKJrtLAX05J680diw4HSFfg7LW56ga7Hrg@mail.gmail.com>
On Tuesday 16 July 2013 17:36:08 Samuel Stirtzel wrote:
> 2013/7/13 Paul Eggleton <paul.eggleton@linux.intel.com>:
> > * Add proper SUMMARY
> > * Break long DESCRIPTION onto multiple lines
> > * Reorder some lines
> >
> > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> > ---
> >
> > meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb | 20
> > ++++++++++++++++++++ 1 file changed, 20 insertions(+)
> > create mode 100644 meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb
> >
> > diff --git a/meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb
> > b/meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb new file mode
> > 100644
> > index 0000000..c4ed5e6
> > --- /dev/null
> > +++ b/meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb
> > @@ -0,0 +1,20 @@
> > +SUMMARY = "Protocol Buffers - structured data serialisation mechanism"
> > +DESCRIPTION = "Protocol Buffers are a way of encoding structured data in
> > an \ +efficient yet extensible format. Google uses Protocol Buffers for
> > almost \ +all of its internal RPC protocols and file formats."
> > +HOMEPAGE = "http://code.google.com/p/protobuf/"
> > +SECTION = "console/tools"
> > +LICENSE = "BSD-3-Clause"
> > +
> > +LIC_FILES_CHKSUM =
> > "file://COPYING.txt;md5=af6809583bfde9a31595a58bb4a24514" +
> > +SRC_URI = "http://protobuf.googlecode.com/files/protobuf-${PV}.tar.gz"
> > +
> > +SRC_URI[md5sum] = "dc84e9912ea768baa1976cb7bbcea7b5"
> > +SRC_URI[sha256sum] =
> > "eac6969b617f397247e805267da2b0db3ff9e5a9163b123503a192fbb5776567" +
> > +EXTRA_OECONF += " --with-protoc=echo"
>
> Hi,
>
> do you know why it doesn't use:
>
> EXTRA_OECONF += "--with-protoc=${STAGING_BINDIR_NATIVE}/protoc"
>
> in combination with DEPENDS += "protobuf-native" in protobuf?
> Instead the recipe that uses protobuf/protoc depends on protobuf and
> protobuf-native.
>
> My assumption is, that the result would the same, and it is currently
> skipping tests for the cross compiled protobuf.
> Or does it archive anything else?
I'm not sure, this bit came from the original protobuf recipe in meta-
virtualization. David, you seem to have written this recipe originally, do you
have any insight into the above?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-07-16 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 14:47 [meta-oe][PATCH 0/3] Add mosh and dependencies Paul Eggleton
2013-07-13 14:47 ` [meta-oe][PATCH 1/3] protobuf: add recipe from meta-virtualization and tweak Paul Eggleton
2013-07-16 15:36 ` Samuel Stirtzel
2013-07-16 17:07 ` Paul Eggleton [this message]
2013-07-13 14:47 ` [meta-oe][PATCH 2/3] libio-pty-perl: add from OE-Classic and update Paul Eggleton
2013-07-13 14:47 ` [meta-oe][PATCH 3/3] mosh: add new recipe for version 1.2.4 Paul Eggleton
2013-07-15 3:54 ` Otavio Salvador
2013-07-15 9:40 ` Paul Eggleton
2013-07-15 12:37 ` [meta-oe][PATCH 0/3] Add mosh and dependencies Joe MacDonald
2013-07-15 15:02 ` Otavio Salvador
2013-07-15 15:36 ` Paul Eggleton
2013-07-15 16:40 ` Otavio Salvador
2013-07-15 17:42 ` Joe MacDonald
[not found] <88701C38B5D07249817D428430999C9128CE412D@sestoex05.enea.se>
2013-07-18 8:18 ` [meta-oe][PATCH 1/3] protobuf: add recipe from meta-virtualization and tweak Samuel Stirtzel
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=2169768.F21dFWYplB@helios \
--to=paul.eggleton@linux.intel.com \
--cc=david.nystrom@enea.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=s.stirtzel@googlemail.com \
/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