Hi all,
We use the CMake files of Protobuf to include the libprotobuf target.
However, in the Protobuf CMakeLists.txt file, the "include(install.cmake)"
at bottom seems to mess up the target_include_directories directive
for libprotobuf, so that my targets do NOT get the specified include
direc
Hi all,
I'm using protobuf in our CMake based projects, and I've encountered a
problem with TARGET_INCLUDE_DIRECTORIES not working as expected. Nominally
if my target APP depens on libprotobuf, the PUBLIC part
of TARGET_INCLUDE_DIRECTORIES should propagate to target APP.
This does not work howe
Hi Feng,
Den måndag 16 maj 2016 kl. 22:32:06 UTC+2 skrev Feng Xiao:
>
>
>
> Could you create a github issue for this? We are happy to accept a pull
> request if you have found a workaround for this problem.
>
The only workaround so far though, is to omit the "include(install.cmake)"
line. But I
Hi all,
Running gRPC v1.0.0 with associated protobuf v3.0.0 and C++ (VS2015). A
code excerpt that did work fine with gRPC v0.14.0 now suddenly fails, and
it is associated with protobuf maps.
Protocol:
message Message {
message Output {
...
}
map outputs = 1;
}
which I then access fro
Never mind, something was messed up with my build. Works fine now
Den lördag 8 oktober 2016 kl. 17:04:11 UTC+2 skrev Robert Bielik:
>
> Hi all,
>
> Running gRPC v1.0.0 with associated protobuf v3.0.0 and C++ (VS2015). A
> code excerpt that did work fine with gRPC v0.14.0 now
