Conan-center-index: [request] paho.mqtt.c/1.3.2

[keysight-daryl]

Package Details

• paho.mqtt.c/1.3.2 & associated paho.mqtt.cpp

The above mentioned version is being released within the next day or two and has already been tagged and merged back to master at the authors github. this version also has removed the oem conan recipe in favor of assuming conan-center is doing a better job keeping it updated. Looking to adopt this new version as soon as possible for a critical project. make us proud!

[keysight-daryl]

Additionally the lead developer Ian Craggs has indicated an interest in helping steer this recipe to accommodate upcoming changes but isn't sure how to get involved on here... developers maintain their own mattermost channel that might be useful in bringing onboard...

https://mattermost.eclipse.org/eclipse/channels/paho

[keysight-daryl]

paho.mqtt.c 1.3.2 was released by Ian Craggs 3 days ago... hoping this gets some priority

[Croydon]

What is required to contribute a 1.3.2 update:

• if not done yet, request early access here: #4 - this is a one time thing per GitHub user
• add 1.3.2 locally to recipes/paho-mqtt-c/config.yml and recipes/paho-mqtt-c/all/conandata.yml
  
  
  
  • if necessary, rebase existing 1.3.1 patches for 1.3.2 (see recipes/paho-mqtt-c/all/conandata.yml and recipes/paho-mqtt-c/all/patches/
  
  
• if a local build passes, e.g. via cd recipes/paho-mqtt-c/all/ && conan create . paho-mqtt-c/1.3.2@ you can create now a pull request

[keysight-daryl]

I'll nudge the Paho lead Ian Craggs to this thread since he had expressed interest in contributing to this project over here and getting things integrated properly...

[keysight-daryl]

I guess this also implies updating to the paho.mqtt.cpp/1.1.1 that is still in progress by Frank Pagliughi (@fpagliughi also on Paho Mattermost)...

[icraggs]

I've requested as per step 1. Now to figure out the others...

[Croydon]

1862 is merged, can be closed now

Thanks for contributing! If you have any further questions don't hesitate to ask any time 😄

[icraggs]

I should add that it's version 1.3.4 which has been contributed because 1.3.2 accidentally introduced a binary backward incompatibility with 1.3.1, and in the process of fixing it I made a mistake with 1.3.3. That's what you get for trying to do things quickly!

[keysight-daryl]

Appears setting the recipe option 'ssl' to True does not ultimately link the library with SSL support enabled. Also noticed regardless of the 'ssl', 'asynchronous' and 'shared' settings it always packages all variants of the library together and so it isn't clear which binary the consuming application ultimately is linking against.

[uilianries]

Appears setting the recipe option 'ssl' to True does not ultimately link the library with SSL support enabled. Also noticed regardless of the 'ssl', 'asynchronous' and 'shared' settings it always packages all variants of the library together and so it isn't clear which binary the consuming application ultimately is linking against.

@keysight-daryl Could you please open a new issue relating it? It can be a bug in that recipe.

[uilianries]

@keysight-daryl never mind, I saw your issue now: #1882