Le 05/11/2014 16:41, Guillaume Déflache a écrit :
You were the fastest to respond so you indeed ought to stay the
maintainer! ;)
;-)
For others' to understand I should have made clear the library itself
builds fine, only the host's `protoc` does not get installed.
It would not help, 2.4.1 of AA worked fine, only the Makefile's new host
macros cause problems.
That patch chunk should be reverted IMHO and only the version changed,
in case someone still needs it (we do not).
Besides there is 2.6.1 now: in my own experience x.y.n tends to be more
stable than z.t.0 for all values of x,y,z,t and n! :)
I just made a quick build using 2.6.1 from github on the openwrt's trunk.
I had to remove the patch completely , and make the according changes on
the Makefile.
Then it built (host+package) without any issues on my debian jessie (I
have to indicate here
that I do not have the libprotobuf nor the libprotobuf-dev .deb
packages installed on this machine.
It created me the ./build_dir/host/protobuf-2.6.1/src/protoc without
issues.
Meanwhile another protobuf-related problem showed up, perhaps someone
can help:
[100%] Building CXX object CMakeFiles/[CENSORED].pb.cc.o
/tmp/ccKFaHTE.s: Assembler messages:
/tmp/ccKFaHTE.s:16516: Error: opcode not supported on this processor:mips1
(mips1) `sync'
make[5]: *** [CMakeFiles/[CENSORED].pb.cc.o] Error 1
Since the snapshot we used previously PKG_USE_MIPS16:=0 also got added,
does that mean we should also use that on all packages that compile
Protocol Buffer generated code and/or link with the PB library?
Or is it necessary/possible to instruct the host protoc to generate
source code for MIPS32? Does PB needs generating CPU-specific C/C++
(instrinsics?) or asm sections?
(We do not need MIPS16 ATM, so any MIPS32 solution would do for us.)
The target platform I'm using now is Ralink RT5350 , so mips24k , is
that OK for you ?
I don't really understand why you have such an error - it look like a
compiler error rather than a protobuf error.
I have yet to build the package with a mips16 target.
Anyway, the patch I used is joined to this mail - if it's OK with you
I'll resend the patch with an official pull-request header.
Thanks ,
Obinou
diff --git a/libs/protobuf/Makefile b/libs/protobuf/Makefile
index 1553a7e..ea2a81f 100644
--- a/libs/protobuf/Makefile
+++ b/libs/protobuf/Makefile
@@ -8,12 +8,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=protobuf
-PKG_VERSION:=2.5.0
+PKG_VERSION:=2.6.1
PKG_RELEASE:=1
-PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
-PKG_SOURCE_URL:=http://protobuf.googlecode.com/files
-PKG_MD5SUM:=a72001a9067a4c2c4e0e836d0f92ece4
+PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
+PKG_SOURCE_URL:=https://github.com/google/protobuf/releases/download/$(PKG_VERSION)/
+PKG_MD5SUM:=f3916ce13b7fcb3072a1fa8cf02b2423
PKG_BUILD_DEPENDS:=protobuf/host
PKG_USE_MIPS16:=0
@@ -33,9 +33,9 @@ define Package/protobuf
endef
define Package/protobuf/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.
+ From package description:
+ "Protocol buffers are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data - think XML, but smaller, faster, and simpler.
+ You define how you want your data to be structured once, then you can use special generated source code to easily write and read your structured data to and from a variety of data streams and using a variety of languages - Java, C++, or Python."
endef
define Host/Compile
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
