Skip to contentSkip to conversation

Add mosh and dependencies

PATCH In review Paul Eggleton 4 participants 13 messages Jul 13, 2013 – Jul 16, 2013

lore
Share & tools
lore

Paul Eggleton

author
#0 lore raw

cover Add mosh and dependencies

Add a recipe for mosh, and for dependencies migrate libio-pty-perl from OE-Classic and bring in protobuf from meta-virtualization.

I considered putting this in meta-networking, however meta-virtualization will still need protobuf and it already depends on meta-oe, and officially meta-networking does not depend on meta-oe so splitting these would not really work with the current layer dependencies.

The following changes since commit c383d6230942bb1558cee02764bced09031cb70f:

llvm3.3: Add zlib dependency and explicitly enable it (2013-07-12 12:12:09 +0200)

are available in the git repository at:

git://git.openembedded.org/meta-openembedded-contrib paule/mosh
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/mosh

Paul Eggleton (3):
protobuf: add recipe from meta-virtualization and tweak
libio-pty-perl: add from OE-Classic and update
mosh: add new recipe for version 1.2.4

 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb    | 29 ++++++++++++++++++++++
 .../recipes-devtools/perl/libio-pty-perl_1.10.bb   | 14 +++++++++++
 .../recipes-devtools/protobuf/protobuf_2.4.1.bb    | 20 +++++++++++++++
 3 files changed, 63 insertions(+)
 create mode 100644 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb
 create mode 100644 meta-oe/recipes-devtools/perl/libio-pty-perl_1.10.bb
 create mode 100644 meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb
Signature · 1 line
1.8.1.2
author
#1 lore raw

PATCH 1/3 protobuf: add recipe from meta-virtualization and tweak

* Add proper SUMMARY
* Break long DESCRIPTION onto multiple lines
* Reorder some lines

Signed-off-by Paul Eggleton <[email protected]>
---
 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
meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb new file +20 -0
new file mode 100644
index 0000000..c4ed5e6
@@ -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"
+
+inherit autotools
+
+BBCLASSEXTEND = "native nativesdk"
Signature · 1 line
1.8.1.2
author
#4 lore raw

PATCH 2/3 libio-pty-perl: add from OE-Classic and update

In reply to Paul Eggleton

* Update to version 1.10
* Set SUMMARY instead of DESCRIPTION
* Put SRC_URI checksums under SRC_URI
* Add LIC_FILES_CHKSUM
* Make LICENSE slightly more specific and add spacing

Signed-off-by Paul Eggleton <[email protected]>
---
 meta-oe/recipes-devtools/perl/libio-pty-perl_1.10.bb | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 meta-oe/recipes-devtools/perl/libio-pty-perl_1.10.bb
meta-oe/recipes-devtools/perl/libio-pty-perl_1.10.bb new file +14 -0
new file mode 100644
index 0000000..88db683
@@ -0,0 +1,14 @@
+SUMMARY = "Perl module for pseudo tty IO"
+SECTION = "libs"
+LICENSE = "Artistic-1.0 | GPL-1.0+"
+LIC_FILES_CHKSUM = "file://META.yml;beginline=7;endline=8;md5=f86a66cc3d9522a227298d6898b181a2"
+
+SRC_URI = "http://www.cpan.org/modules/by-module/IO/IO-Tty-${PV}.tar.gz"
+
+SRC_URI[md5sum] = "46baec86a145e57f0ec661fa412b097c"
+SRC_URI[sha256sum] = "31a6e21ad187ec5ea93c2b898d6b3519647c5fce9f394b6d3c05a1f7c3f6f8b1"
+
+S = "${WORKDIR}/IO-Tty-${PV}"
+
+inherit cpan
+
Signature · 1 line
1.8.1.2
author
#5 lore raw

PATCH 3/3 mosh: add new recipe for version 1.2.4

In reply to Paul Eggleton
Signed-off-by Paul Eggleton <[email protected]>
---
 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb | 29 +++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb
meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb new file +29 -0
new file mode 100644
index 0000000..e9881bc
@@ -0,0 +1,29 @@
+SUMMARY = "Remote shell supporting roaming and high-latency connections"
+DESCRIPTION = "Remote terminal application that allows roaming, supports \
+intermittent connectivity, and provides intelligent local echo and line \
+editing of user keystrokes. Mosh is a replacement for SSH. It's more \
+robust and responsive, especially over Wi-Fi, cellular, and \
+long-distance links."
+HOMEPAGE = "http://mosh.mit.edu"
+LICENSE = "GPLv3+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
+
+DEPENDS = "protobuf-native protobuf ncurses zlib libio-pty-perl openssl"
+
+SRC_URI = "http://mosh.mit.edu/mosh-${PV}.tar.gz"
+
+SRC_URI[md5sum] = "c2d918f4d91fdc32546e2e089f9281b2"
+SRC_URI[sha256sum] = "e74d0d323226046e402dd469a176075fc2013b69b0e67cea49762c957175df46"
+
+inherit autotools
+
+PACKAGE_BEFORE_PN += "${PN}-server"
+FILES_${PN}-server = "${bindir}/mosh-server"
+
+# mosh uses SSH to authenticate and the client uses OpenSSH-specific features
+RDEPENDS_${PN} += "openssh-ssh"
+# The server seemed not to work with dropbear either
+RDEPENDS_${PN}-server += "openssh-sshd"
+# Note: the server also requires a UTF-8 locale, but there's no way
+# to add a dependency for this
+
Signature · 1 line
1.8.1.2
#6 lore raw

Re: [meta-oe][PATCH 3/3] mosh: add new recipe for version 1.2.4

Quoted 30 lines · Paul Eggleton
Signed-off-by Paul Eggleton <[email protected]>
---
 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb | 29 +++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb
meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb new file +18 -0
new file mode 100644
index 0000000..e9881bc
@@ -0,0 +1,29 @@
+SUMMARY = "Remote shell supporting roaming and high-latency connections"
+DESCRIPTION = "Remote terminal application that allows roaming, supports \
+intermittent connectivity, and provides intelligent local echo and line \
+editing of user keystrokes. Mosh is a replacement for SSH. It's more \
+robust and responsive, especially over Wi-Fi, cellular, and \
+long-distance links."
+HOMEPAGE = "http://mosh.mit.edu"
+LICENSE = "GPLv3+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
+
+DEPENDS = "protobuf-native protobuf ncurses zlib libio-pty-perl openssl"
+
+SRC_URI = "http://mosh.mit.edu/mosh-${PV}.tar.gz"
+
+SRC_URI[md5sum] = "c2d918f4d91fdc32546e2e089f9281b2"
+SRC_URI[sha256sum] = "e74d0d323226046e402dd469a176075fc2013b69b0e67cea49762c957175df46"
+
+inherit autotools

meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb line 28

Quoted 10 lines
meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb new file +10 -0
+
+PACKAGE_BEFORE_PN += "${PN}-server"
+FILES_${PN}-server = "${bindir}/mosh-server"
+
+# mosh uses SSH to authenticate and the client uses OpenSSH-specific features
+RDEPENDS_${PN} += "openssh-ssh"
+# The server seemed not to work with dropbear either
+RDEPENDS_${PN}-server += "openssh-sshd"
+# Note: the server also requires a UTF-8 locale, but there's no way
+# to add a dependency for this

I'd put this as a WARNING and on the top of the recipe or something so it is easily visible.

--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750

author
#7 lore raw

Re: [meta-oe][PATCH 3/3] mosh: add new recipe for version 1.2.4

Quoted 6 lines · On Monday 15 July 2013 00:54:32 Otavio Salvador wrote:

On Sat, Jul 13, 2013 at 11:47 AM, Paul Eggleton

meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb line 28

Quoted 2 lines
meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb new file +2 -0
+# Note: the server also requires a UTF-8 locale, but there's no way
+# to add a dependency for this

I'd put this as a WARNING and on the top of the recipe or something so it is easily visible.

OK, I've moved the comment to the top and reformatted it slightly on the branch. Note that it's not a disaster if the user forgets to do this - they'll soon find out at runtime when it doesn't work, and the error mosh produces is thankfully clear on what is missing.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#8 lore raw
In reply to Paul Eggleton
Quoted 7 lines · [[oe] [meta-oe][PATCH 0/3] Add mosh and dependencies] On 13.07.13 (Sat 15:47)…

Add a recipe for mosh, and for dependencies migrate libio-pty-perl from OE-Classic and bring in protobuf from meta-virtualization.

I considered putting this in meta-networking, however meta-virtualization will still need protobuf and it already depends on meta-oe, and officially meta-networking does not depend on meta-oe so splitting these would not really work with the current layer dependencies.

That's not strictly true anymore, actually. It was my intent and I think there's value in it, but CRDA (already in meta-networking) depends on python-m2crypto (in meta-oe). I discovered it in my world build a few weeks ago and hadn't yet managed to get round to seeing if there was a clean way to separate the two.

I absolutely don't want the stated intent that meta-networking be standalone be a barrier to adding packages to it that clearly belong to it.

That's my way of saying I've no objection right now to including this in meta-net.

-J.

Quoted 24 lines

The following changes since commit c383d6230942bb1558cee02764bced09031cb70f:

llvm3.3: Add zlib dependency and explicitly enable it (2013-07-12 12:12:09 +0200)

are available in the git repository at:

git://git.openembedded.org/meta-openembedded-contrib paule/mosh
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/mosh

Paul Eggleton (3):
protobuf: add recipe from meta-virtualization and tweak
libio-pty-perl: add from OE-Classic and update
mosh: add new recipe for version 1.2.4

 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb    | 29 ++++++++++++++++++++++
 .../recipes-devtools/perl/libio-pty-perl_1.10.bb   | 14 +++++++++++
 .../recipes-devtools/protobuf/protobuf_2.4.1.bb    | 20 +++++++++++++++
 3 files changed, 63 insertions(+)
 create mode 100644 meta-oe/recipes-connectivity/mosh/mosh_1.2.4.bb
 create mode 100644 meta-oe/recipes-devtools/perl/libio-pty-perl_1.10.bb
 create mode 100644 meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb
Signature · 2 lines
-Joe MacDonald.
:wq
#9 lore raw
Quoted 16 lines · Joe MacDonald
Quoted 7 lines · [[oe] [meta-oe][PATCH 0/3] Add mosh and dependencies] On 13.07.13 (Sat 15:47)…

Add a recipe for mosh, and for dependencies migrate libio-pty-perl from OE-Classic and bring in protobuf from meta-virtualization.

I considered putting this in meta-networking, however meta-virtualization will still need protobuf and it already depends on meta-oe, and officially meta-networking does not depend on meta-oe so splitting these would not really work with the current layer dependencies.

That's not strictly true anymore, actually. It was my intent and I think there's value in it, but CRDA (already in meta-networking) depends on python-m2crypto (in meta-oe). I discovered it in my world build a few weeks ago and hadn't yet managed to get round to seeing if there was a clean way to separate the two.

Quoted 6 lines

I absolutely don't want the stated intent that meta-networking be standalone be a barrier to adding packages to it that clearly belong to it.

That's my way of saying I've no objection right now to including this in meta-net.

I agree; maybe we could add those inside meta-oe subdir? so people can opt in enable them or not.

--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750

author
#10 lore raw
Quoted 4 lines · On Monday 15 July 2013 12:02:59 Otavio Salvador wrote:

On Mon, Jul 15, 2013 at 9:37 AM, Joe MacDonald

Quoted 1 line · <[email protected]> wrote:

[[oe] [meta-oe][PATCH 0/3] Add mosh and dependencies] On 13.07.13 (Sat

Quoted 18 lines · 15:47) Paul Eggleton wrote:
Quoted 18 lines
Quoted 7 lines

Add a recipe for mosh, and for dependencies migrate libio-pty-perl from OE-Classic and bring in protobuf from meta-virtualization.

I considered putting this in meta-networking, however meta-virtualization will still need protobuf and it already depends on meta-oe, and officially meta-networking does not depend on meta-oe so splitting these would not really work with the current layer dependencies.

That's not strictly true anymore, actually. It was my intent and I think there's value in it, but CRDA (already in meta-networking) depends on python-m2crypto (in meta-oe). I discovered it in my world build a few weeks ago and hadn't yet managed to get round to seeing if there was a clean way to separate the two.

I absolutely don't want the stated intent that meta-networking be standalone be a barrier to adding packages to it that clearly belong to it.

Quoted 5 lines
Quoted 2 lines

That's my way of saying I've no objection right now to including this in meta-net.

I agree; maybe we could add those inside meta-oe subdir? so people can opt in enable them or not.

Sorry Otavio, what are you suggesting exactly?

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#11 lore raw
Quoted 24 lines · Paul Eggleton
Quoted 4 lines · On Monday 15 July 2013 12:02:59 Otavio Salvador wrote:

On Mon, Jul 15, 2013 at 9:37 AM, Joe MacDonald

Quoted 1 line · <[email protected]> wrote:

[[oe] [meta-oe][PATCH 0/3] Add mosh and dependencies] On 13.07.13 (Sat

Quoted 18 lines · 15:47) Paul Eggleton wrote:
Quoted 18 lines
Quoted 7 lines

Add a recipe for mosh, and for dependencies migrate libio-pty-perl from OE-Classic and bring in protobuf from meta-virtualization.

I considered putting this in meta-networking, however meta-virtualization will still need protobuf and it already depends on meta-oe, and officially meta-networking does not depend on meta-oe so splitting these would not really work with the current layer dependencies.

That's not strictly true anymore, actually. It was my intent and I think there's value in it, but CRDA (already in meta-networking) depends on python-m2crypto (in meta-oe). I discovered it in my world build a few weeks ago and hadn't yet managed to get round to seeing if there was a clean way to separate the two.

I absolutely don't want the stated intent that meta-networking be standalone be a barrier to adding packages to it that clearly belong to it.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

That's my way of saying I've no objection right now to including this in meta-net.

I agree; maybe we could add those inside meta-oe subdir? so people can opt in enable them or not.

Sorry Otavio, what are you suggesting exactly?

To have a meta-networking/meta-oe with recipes which requires it.

--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750

#12 lore raw
Quoted 29 lines · [Re: [oe] [meta-oe][PATCH 0/3] Add mosh and dependencies] On 13.07.15 (Mon…
Quoted 27 lines · Paul Eggleton
Quoted 4 lines · On Monday 15 July 2013 12:02:59 Otavio Salvador wrote:

On Mon, Jul 15, 2013 at 9:37 AM, Joe MacDonald

Quoted 1 line · <[email protected]> wrote:

[[oe] [meta-oe][PATCH 0/3] Add mosh and dependencies] On 13.07.13 (Sat

Quoted 21 lines · 15:47) Paul Eggleton wrote:
Quoted 20 lines
Quoted 7 lines

Add a recipe for mosh, and for dependencies migrate libio-pty-perl from OE-Classic and bring in protobuf from meta-virtualization.

I considered putting this in meta-networking, however meta-virtualization will still need protobuf and it already depends on meta-oe, and officially meta-networking does not depend on meta-oe so splitting these would not really work with the current layer dependencies.

That's not strictly true anymore, actually. It was my intent and I think there's value in it, but CRDA (already in meta-networking) depends on python-m2crypto (in meta-oe). I discovered it in my world build a few weeks ago and hadn't yet managed to get round to seeing if there was a clean way to separate the two.

I absolutely don't want the stated intent that meta-networking be standalone be a barrier to adding packages to it that clearly belong to it.

That's my way of saying I've no objection right now to including this in meta-net.

Quoted 6 lines
Quoted 4 lines
Quoted 2 lines

I agree; maybe we could add those inside meta-oe subdir? so people can opt in enable them or not.

Sorry Otavio, what are you suggesting exactly?

To have a meta-networking/meta-oe with recipes which requires it.

Oh. That's an interesting idea. I guess the argument against that is the support infrastructure has a reasonable home in meta-oe and nobody wants meta-oe to depend on meta-networking. I do think that having some mechanism for keeping meta-net reasonably standalone but still not full of stuff that's on there to satisfy dependencies is good, though. Haven't really thought much about this yet, though.

-J.

Quoted 9 lines

--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Signature · 2 lines
-Joe MacDonald.
:wq
#2 lore raw

Re: [meta-oe][PATCH 1/3] protobuf: add recipe from meta-virtualization and tweak

In reply to Paul Eggleton

2013/7/13 Paul Eggleton <[email protected]>:

Quoted 22 lines

* Add proper SUMMARY
* Break long DESCRIPTION onto multiple lines
* Reorder some lines

Signed-off-by Paul Eggleton <[email protected]>
---
 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
meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb new file +6 -0
new file mode 100644
index 0000000..c4ed5e6
@@ -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"

meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb line 16

Quoted 10 lines
meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb new file +10 -0
+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?

--
Regards
Samuel

author
#3 lore raw

Re: [meta-oe][PATCH 1/3] protobuf: add recipe from meta-virtualization and tweak

Quoted 42 lines · On Tuesday 16 July 2013 17:36:08 Samuel Stirtzel wrote:

2013/7/13 Paul Eggleton <[email protected]>:

Quoted 32 lines

* Add proper SUMMARY
* Break long DESCRIPTION onto multiple lines
* Reorder some lines

Signed-off-by Paul Eggleton <[email protected]>

---

 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
(quoted diff) +0 -0

b/meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb new file mode 100644
index 0000000..c4ed5e6

meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb new file +2 -0
@@ -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."

meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb new file +5 -0
+HOMEPAGE = "http://code.google.com/p/protobuf/"
+SECTION = "console/tools"
+LICENSE = "BSD-3-Clause"
+
+LIC_FILES_CHKSUM =

"file://COPYING.txt;md5=af6809583bfde9a31595a58bb4a24514" +

meta-oe/recipes-devtools/protobuf/protobuf_2.4.1.bb new file +4 -0
+SRC_URI = "http://protobuf.googlecode.com/files/protobuf-${PV}.tar.gz"
+
+SRC_URI[md5sum] = "dc84e9912ea768baa1976cb7bbcea7b5"
+SRC_URI[sha256sum] =
Quoted 2 lines

"eac6969b617f397247e805267da2b0db3ff9e5a9163b123503a192fbb5776567" + +EXTRA_OECONF += " --with-protoc=echo"

Hi,

do you know why it doesn't use:

EXTRA_OECONF += "--with-protoc=${STAGING_BINDIR_NATIVE}/protoc"

Quoted 7 lines

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

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre