conan-io / conan-center-index

Recipes for the ConanCenter repository
https://conan.io/center
MIT License
921 stars 1.66k forks source link

[request] open62541pp/0.4.1 #18540

Open ErikTempelaarVO opened 11 months ago

ErikTempelaarVO commented 11 months ago

Package Name/Version

open62541pp/0.4.1

Webpage

https://open62541pp.github.io/open62541pp/

Source code

https://github.com/open62541pp/open62541pp

Description of the library/tool

C++ wrapper of the amazing open62541 OPC UA library

High-level and easy to use classes similar to the Python opcua/asyncua API: opcua::Server opcua::Client opcua::Node Safe wrapper classes for open62541 UA* types to prevent memory leaks Native open62541 objects can be accessed using the handle() method of the wrapping classes Extensible type conversion system to convert arbitrary types to/from native UA* types Cross-platform (tested on Windows, Linux and MacOS) Compatible with all stable open62541 versions ≥ v1.0 Easy installation and integration with CMake Use modern C++ (C++ 17) and best practices Less hurdle to get started with OPC UA

I'd like to use this library and consume it via conan, preferably via conan-center.

Library developer is open to this idea. https://github.com/open62541pp/open62541pp/issues/20#issuecomment-1512697890 What is the preferred location for the recipe? With the source code, or separate in CCI? Or both?

I already have the basics working in my own fork but I am unsure how to proceed.

valgur commented 11 months ago

What is the preferred location for the recipe? With the source code, or separate in CCI? Or both?

Adding the recipe to CCI should be sufficient, but additionally including it in the source repo can have some benefits as well:

  1. Allows for more control over the recipe, i.e. can be less stringent about backwards compatibility, for example.
  2. Adds support for settting the package in editable mode, which allows the package to be edited simultaneously with dependent packages.
  3. Can provide custom versions of recipes for dependencies with the repo, if necessary (an example). Can be useful during development, in cases where a recipe has not been published to CCI yet.

I already have the basics working in my own fork but I am unsure how to proceed.

I encourage you to open a PR. It looks quite complete already. With some minor touches here and there it should be good to go, I think.

lbckmnn commented 8 months ago

@ErikTempelaarVO Are you still working on this? Otherwise I might give this a try myself :)

ErikTempelaarVO commented 7 months ago

@lbckmnn I'm sorry for the late reply, I don't recall being notified of your message. Please have a go at it!

I'm currently consuming this library as submodule in my project, but I'd love to replace it with a conan recipe.

oliver commented 5 months ago

@valgur you wrote:

I encourage you to open a PR. It looks quite complete already. With some minor touches here and there it should be good to go, I think.

I'm not entirely certain what you meant by that. Where should this PR be opened, in your opinion? In https://github.com/conan-io/conan-center-index or in https://github.com/open62541pp/open62541pp ?

valgur commented 5 months ago

@oliver Here, on CCI.

ErikTempelaarVO commented 3 months ago

In the meantime several new version have been released:

https://github.com/open62541pp/open62541pp/tags

oliver commented 3 months ago

FYI: I have upgraded the Conan recipe to 0.12.0, at https://github.com/oliver/open62541pp/tree/feat/conan-recipe . I am currently using that Conan recipe successfully.