Following up my own post ...
On Wednesday, January 21, 2015 at 5:04:25 PM UTC+11, Chris Johns wrote:
>
>
> The first are errors related to Atromics. We are adding -fpermissive to
> make then warning. Here are a few of the many warnings we are seeing:
>
> from ../../protobuf.git/s
On Thu Jan 22 2015 at 4:53:53 PM wrote:
>
> As a new user, we still have need (C++ target) for default values, as well
> as required fields (e.g., message headers for embedded target).
>
> 1) It appears that you are completely removing the default/required
> capability from the proto3 language.
As a new user, we still have need (C++ target) for default values, as well
as required fields (e.g., message headers for embedded target).
1) It appears that you are completely removing the default/required
capability from the proto3 language. Is this correct ?
2) Will the proto2 language be
Updates:
Status: WontFix
Owner: xiaof...@google.com
Comment #2 on issue 686 by xiaof...@google.com: Protoc does not provide a
dependency manifest output file for build tools like make
https://code.google.com/p/protobuf/issues/detail?id=686
Hi, could you help file this issue on
Comment #14 on issue 447 by mend...@gmail.com: No C++11 move constructors
https://code.google.com/p/protobuf/issues/detail?id=447
So a move constructor (eventually marked as noexcept) is not a peformance
gain? Right!
--
You received this message because this project is configured to send all
Comment #1 on issue 686 by haberl...@gmail.com: Protoc does not provide a
dependency manifest output file for build tools like make
https://code.google.com/p/protobuf/issues/detail?id=686
this is what we're using - maybe can be built upon:
https://github.com/machinekit/machinekit/blob/master
I got the same error when building for x64. The custom build command for
proto files in the test projects are hard-coded to work with the default
intermediate build directory in the Win32 configuration. You need to change
the command property of the Custom Build Tool for all the proto files to
