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
As explained in the issue description and the comments following, the issue is that the library don't have a way to express it's binaries locations once built using CMake. With the previous visual studio files on windows, the paths are fixed so the issue here was to complete the FindProtobuf module to work with 64bit versions.
Now that Protobuf provides CMake files, the paths do not match any FindProtobuf module way of searching anymore. The current best way to fix this is to provide packaging files instead of assuming the user have a working FindProtobuf module. This way, the packaging files will guide CMake and the user code can use either path variables generated on build OR (better solution) directly imported targets generated. Imported targets are easier to work with for the user.
This would also make FindProtobuf module in CMake repository obsolete for Protobuf 3.x+ and would make Protobuf more independant.
The text was updated successfully, but these errors were encountered:
@podsvirov has done quite some work to refine the cmake support. I believe installation is supported now but I don't know how it works with FindProtobuf. Feel free to send us a patch to tweak the cmake scripts to make it work better with FindProtobuf.
The *-config and *-package files should make it work as long as the user provides the package search path to the cmake directory. I will try these changes when I will have time but don't hold your breath, I'm in the middle of heavy developments and will not have time to focus on this in the coming weeks.
This is an issue specific to 3.x version of Protobuf.
As pointed in this FindProtobuf CMake module issue: http://public.kitware.com/Bug/view.php?id=14833
As explained in the issue description and the comments following, the issue is that the library don't have a way to express it's binaries locations once built using CMake. With the previous visual studio files on windows, the paths are fixed so the issue here was to complete the FindProtobuf module to work with 64bit versions.
Now that Protobuf provides CMake files, the paths do not match any FindProtobuf module way of searching anymore. The current best way to fix this is to provide packaging files instead of assuming the user have a working FindProtobuf module. This way, the packaging files will guide CMake and the user code can use either path variables generated on build OR (better solution) directly imported targets generated. Imported targets are easier to work with for the user.
This would also make FindProtobuf module in CMake repository obsolete for Protobuf 3.x+ and would make Protobuf more independant.
The text was updated successfully, but these errors were encountered: