-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add Open62541 recipe v1.0.3 and v1.1.3 #3786
Conversation
Signed-off-by: Dovydas Girdvainis <dovydas.girdvainis@hahn-schickard.de>
Signed-off-by: Dovydas Girdvainis <dovydas.girdvainis@hahn-schickard.de>
Signed-off-by: Dovydas Girdvainis <dovydas.girdvainis@hahn-schickard.de>
Signed-off-by: Dovydas Girdvainis <dovydas.girdvainis@hahn-schickard.de>
…figs Signed-off-by: Dovydas Girdvainis <dovydas.girdvainis@hahn-schickard.de>
…options Signed-off-by: Dovydas Girdvainis <dovydas.girdvainis@hahn-schickard.de>
Signed-off-by: Dovydas Girdvainis <dovydas.girdvainis@hahn-schickard.de>
Some configurations of 'open62541/1.1.3' failed in build 23 (
|
…ckets, set hardening to True remove clang 9 support
Option testing reportI finished testing both v1.0.3 and v1.1.3 packages with all of the options enabled (I ran separate tests for each encryption, multi-threading and pub sub option with other options set to From my point of view if all options work on the same time, there is no reason why they should not work on there own, since all of the options that require something else are already handle during the configuration, but again no guaranty... Regarding Clang 9 support
It seems that I have mixed up the reports between 1.0.3 and 1.1.3. Regarding Cpp compatibility support for 1.0.3I removed it due to the fact that I would have to patch quite a bit of source files to get rid of |
Some configurations of 'open62541/1.1.3' failed in build 24 (
|
Some configurations of 'open62541/1.1.3' failed in build 25 (
|
All green in build 26 (
|
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.
Some comments about some <=
signs, not sure if they should be <
according to the messages in the ConanInvalidConfiguration
errors. 🤔
Some configurations of 'open62541/1.0.3' failed in build 27 (
|
All green in build 28 (
|
* master: (73 commits) (conan-io#3878) opengl: support FreeBSD (conan-io#3882) [system-cci] Fix hooks (conan-io#3881) [szip] Fix hooks (conan-io#3880) [tcl] Fix hooks (conan-io#3866) xorg: add freebsd packages (conan-io#3825) Adds baikal-p7 5.6 (conan-io#3758) minimal recipe for pciutils/3.7.0 (conan-io#3211) added recipe for extra-cmake-modules (conan-io#3870) tl: fix compiler version check again (conan-io#3865) bump eigen/3.3.9 (conan-io#3864) add functionalplus/0.2.13-p0 bump fmt/7.1.3 (conan-io#3694) (conan-io#3858) fix: zulu-openjdk package info (conan-io#3836) gmp: bump + enable building static libraries on MSVC (conan-io#3812) Add logr v0.1.0 (conan-io#3786) add Open62541 recipe v1.0.3 and v1.1.3 (conan-io#3696) openh264: refactor + add 2.1.1 release (conan-io#3607) add botan/2.17.2 (conan-io#3854) Add PEGTL 3.0.0 (conan-io#3859) bump spdlog/1.8.2 ...
Description
as @prince-chrismc recommended in his comment, I am refactoring my work from PR #1687 with the work @syoliver did in PR #1856 to hopefully bring the best of both worlds and finally release the definative Open62541 recipe.
This PR:
pro-mdnsd/0.8.4
as a conan dependency instead of git sub-module.UA-Nodeset
git sub-module as it is required for Non-minimal setups (conan optionnamespace_zero
is not set to MINIMAL).Questions to conan-io communtiy:
To Do:
Specify library name and version: open62641/1.0.3 and open62641/1.1.3
conan-center hook activated.