Thanks for your hints. But there's still one thing not clear for me:
I don't need the protoc compiler as powerpc executable, just the
runtime libs. Is there a way to give an option (build-target) to
or make, to build just theese? I didn't see one after having a quick
on configure and the generated Makefile. Or will the --with-protoc
have this effect?
On 1 Sep., 18:25, Kenton Varda <ken...@google.com> wrote:
> Use the --with-protoc option to configure to tell it to use a particular
> protoc binary when building (rather than attempt to execute the one it just
> Other than that, cross-compiling works the same as with any
> automake/autoconf package. E.g. I have cross-compiled Windows binaries on a
> Mac machine using:
> ./configure --with-protoc=/usr/bin/protoc --host=i386-mingw32
> Depending on your setup, you may need to specify more stuff. See
> INSTALL.txt for detailed instructions.
> Note that protoc's output is identical on all platforms.
> On Tue, Sep 1, 2009 at 7:28 AM, Makulik <guenther.maku...@kathrein.de>wrote:
> > Hi,
> > I need to use protobuf in a cross-compiling environment.
> > The .proto files should be compiled with an x86 version
> > of protoc, but the outputs should be compiled with a
> > powerpc gcc and of course linked with an appropriate
> > version of the protobuf runtime libs.
> > What's the best approach just to configure, compile
> > and install the runtime libs for the powerpc target
> > (I have a shelltool [ltib] that spoofs all the standard dirs like
> > /usr/local/... and allows to build for the cross-target)?
> > WBR
> > Günther
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to
For more options, visit this group at