That's part of how libtool handles execution of uninstalled binaries.
http://www.gnu.org/software/libtool/manual/libtool.html#Linking-executables
On Wed, Jan 30, 2013 at 11:19 PM, Mohit Jaggi wrote:
> Hi All,
> I am wondering what lt-protoc binary file is? It is in src/.libs when we
> build pro
> Those messages are optional. You will only send one, the one that you
> actually add. The others take up no space in the serialized data stream.
>
> Chris
>
Hi Chris,
of course, you're right! I'm only new on this way of implementation! :-)
But I will adapt to it, if it's the best way!
Dan
I actually got to the bottom of this and it was a pretty silly mistake. The
problem was in string conversions:
My message callback looks like this:
messageHandler(const RWCString& buffer_)
and the parse method signature is this:
ParseFromString(const string& data);
So to convert between the
Comment #9 on issue 119 by j.ignaci...@gmail.com: TYPE_BOOL collides with
MacOS macro
http://code.google.com/p/protobuf/issues/detail?id=119
I tried several tricks to solve this in the google source, but in the end,
I settled on a #undef in any generated *.pb.cc which triggers a compilation
