Oh, to clarify - it is the total size of my app that is 80kb, try to build it 
on your target to find out the size cost in your case


-----Original Message-----
From: protobuf@googlegroups.com [mailto:proto...@googlegroups.com] On Behalf Of 
Sent: den 9 februari 2009 21:57
To: Protocol Buffers
Subject: Re: Using protocol buffers in 16 bit environments: Suport for 16 bit 

Thanks Kenton, Magnus,

On a closer look I see your points. I neither have the code space
available nor the necessary feature support in the embedded C++
compiler to handle the generated code or rebuild the lib. Even at 80Kb
(for protoc_c) that's a fair proportion of available RAM gone. I'm
back to hand coding. Thanks again.

On Feb 9, 11:20 pm, shaw.softw...@gmail.com wrote:
> I considering using protocol buffers to communicate between a PC and a
> 16 but embedded environment (using C++). Protocol buffers support only
> 32 bit ints, known as longs on   on the embedded platform.
> I'm imagining I can either
> 1) include some conditonal typdefs to sort this out, on the embedded
> side redefining int in the generated protoc classes as long
> or
> 2) attempt to extend protocol buffers to support 16 bit ints
> The later,while cleaner and more efficient for the  transmitted data,
> might be beyond my capabilities. Any advice out there?
> Thanks,
> Peter

You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to