Apparently (via private correspondence), using machine/endian.h
instead of mach/endian.h worked -- so i added that to the list of
endianness-detection headers.
I dunno if there's some sort of FAQ on xcompiling protobuf, but there
is a general problem that the protoc_c compiler must be runnable
I built libprotobuf for the iphone (must be static for app store
apps). It's about 3mb. This results in a significant footprint
increase for applications. Is there any way to reduce this?
Thanks,
Marc
--~--~-~--~~~---~--~~
You received this message because you
Sorry, our implementation was designed for servers where binary footprint is
not a big deal. Maybe try using protobuf-c?
On Tue, Mar 3, 2009 at 7:09 AM, marc vaill...@cis.jhu.edu wrote:
I built libprotobuf for the iphone (must be static for app store
apps). It's about 3mb. This results in
[+dave]
On Tue, Mar 3, 2009 at 11:33 AM, marc vaill...@cis.jhu.edu wrote:
On Mar 3, 1:42 pm, Kenton Varda ken...@google.com wrote:
Sorry, our implementation was designed for servers where binary footprint
is
not a big deal. Maybe try using protobuf-c?
Ok thanks. Getting the
Without the actual config.log it's hard to tell what's going on. You
may send it to me privately if you want.
If you have a working endian.h or mach/endian.h, we shouldn't need
to run a test program. but i have never written an iphone app, so i
have really no idea if they have such a header.
