You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while building ViSQOL with CMake against a CMake-built protobuf I noticed that ViSQOL uses protobuf-internal headers like src/google/protobuf/stubs/statusor.h which won't be available in a CMake-protobuf installation.
I opened an issue in protocolbuffers/protobuf#7358 and asked to align both: the CMake and Bazel buildsystem in terms of installed or available headers. Based on the outcome you might lose access to StatusOr.
Are you aware of any replacement for StatusOr (e.g. in abseil-cpp)?
Thanks,
Gregor
The text was updated successfully, but these errors were encountered:
Hi, I'm not aware of a replacement for StatusOr, and I have seen several projects using protobuf/stubs/statusor.h; I think the issue you opened up in the protobuf repo should be enlightening. For your situation it seems the hacky workaround will be to manually copy the headers or use a search path.
gjasny
added a commit
to gjasny/visqol
that referenced
this issue
Oct 2, 2020
Hello,
while building ViSQOL with CMake against a CMake-built protobuf I noticed that ViSQOL uses protobuf-internal headers like
src/google/protobuf/stubs/statusor.h
which won't be available in a CMake-protobuf installation.I opened an issue in protocolbuffers/protobuf#7358 and asked to align both: the CMake and Bazel buildsystem in terms of installed or available headers. Based on the outcome you might lose access to
StatusOr
.Are you aware of any replacement for
StatusOr
(e.g. in abseil-cpp)?Thanks,
Gregor
The text was updated successfully, but these errors were encountered: