On Monday, 21 October 2019 12:57:16 UTC+5:30, sridevi i wrote:
>
> I am unable to configure protobuff using cmake on windows 10 following the
> link "
> https://github.com/protocolbuffers/protobuf/blob/master/cmake/README.md;
> using visual studio 14.
> Showing the error : LINK : fatal error
I am unable to configure protobuff using cmake on windows 10 following the
link "
https://github.com/protocolbuffers/protobuf/blob/master/cmake/README.md;
using visual studio 14.
Showing the error : LINK : fatal error LNK1104: cannot open file
'LIBCMT.lib'
error file is attached ,
the library
Hi fellows,
I am running an application on Redhat which is linked with protobuf
generated code. But this particular app doesn't use protobuf at all - it is
just linked with library which in its turn linked with protobuf files.
When I run my app under valgrind it shows many many small leaks.
Those "leaks" are harmless because they're not really leaks, just memory
that is still reachable at program exit. If you really want to make them
disappear from the Valgrind output, though, you can try calling
google::protobuf::ShutdownProtobufLibrary() (from
src/google/protobuf/stubs/common.h)
I am on a project where we are looking to create a standard .proto file
that can be used by multiple vendors to create interoperable
implementations of an open, standard interface that we are developing. The
.proto file would be specified in the standard, along with pointers to the
Google
I am on a project where we are looking to create a standard .proto file
that can be used by multiple vendors to create interoperable
implementations of an open, standard interface that we are developing. The
.proto file would be specified in the standard, along with pointers to the
Google
Thanks Adam! Again you are of great help.
That's what I expected. I want them to dissappear because i am trying
catch possible real leaks and protobuf messages just flooding the valgrind
log.
Thanks.
P.S. I already implemented your suggestion and it worked
#include
