Hey,
without having a closer look it sounds like you could use the
'HostBuild'-functionality for building required host tools in advance.
I can recommend the 'fribidi' or 'lua' package to have a look at how
HostBuilds work. The file 'include/host-build.mk' might contribute
towards better understanding as well.
mirko
On Tue, 7 Jun 2011 11:43:56 +0200, Obinou wrote:
Hello,
This patch adds the Protobuf library into feeds/packages.
Protobuf ( http://code.google.com/p/protobuf/ ) is 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.
It's vaguely similar to rpcgen, in a (wicked) way, but for C++/python
or Java
(Here in OpenWRT only C++ is built)
I've tested it on Atheros and BCM63xx plateforms, on OpenWRT trunk.
Note:
I'm *not* very happy with my work on this:
Building this package create the "protoc" tool to create some C++
files.
But since it is cross-compiling, of course the protoc tool that is
build is made for the target.
So, later during the build, when the protoc tool is invoked on the
host the compilation failed, since it's not able to execute this
binary file.
The solution I have now is to force the user to have the protobuf
package installed on its development host, and force its usage by
passing a ./configure option.
Rather unacceptable....
So I'm taking any advice or exemple concerning this problem, and I
will create a second version of this patch to correct this behaviour.
Thanks.
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
