-
Notifications
You must be signed in to change notification settings - Fork 34
Be compatible with all in-use cppzmq versions. #561
Be compatible with all in-use cppzmq versions. #561
Conversation
Looks like there is a problem with cppzmq from debian 7 repos:
|
@mliszcz Okay so I'll add a test for disconnect and resurrect the manual cppzmq installation. Nobody should use debian7 (wheezy) anymore as it is EOL, but let's not get distracted here. |
Why do you need a test for disconnect? Maybe just revert |
@mliszcz The test is required so that people how are trying to compile it on debian 7 don't get a compile error but an error message from cmake. |
5a82103
to
5923aab
Compare
29f0eb6
to
4675d56
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
I think the issue with zmq disconnect is actually due to a recent refactoring change when ZmqEventConsumer::disconnect_socket() method was created. |
@bourtemb The |
4675d56
to
cf1612b
Compare
@bourtemb Turns out we already had the ZMQ_HAS_DISCONNECT define. I've done as you suggested and also removed my try compile as we can how handle both cases properly. |
cf1612b
to
7213bc7
Compare
…cppzmq versions Depending on the cppzmq version from https://github.com/zeromq/cppzmq the operator void* is either implicit or explicit. We could now add a feature check in cmake to check for that and use code paths for each variant. But we could also be really pragmatic and just use a unconditional static_cast<void*>. Idea and initial patch by Michal Liszcz.
Although we only call the function disconnect_socket if the define is true the compiler still sees the code.
7213bc7
to
a637035
Compare
Follow up from #530.
Close #499.
Close #273.
Close #535.