-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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 recipe for libignition-sensors4 #14313
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/example/libignition-sensors:
|
…nition-sensors/meta.yaml
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@wolfv @Tobias-Fischer @j-rivero @JShep1 I listed yourself as additional maintainers, please confirm if this is ok for you, or if you prefer not to be a mantainer of this package. |
I'm fine with that! |
macOS fails with:
We probably need to target 10.13 due to the use of recent C++ features. |
@conda-forge/help-c-cpp The PR is now ready for review. See the fist comment for an overview, and for the explanation of why the macOS build is failing and it make sense to merge the PR regardless. |
For the time being I removed your names, once the PR is merged we can add them back if you want, thanks! |
I'm happy, too. One remark, last time we merged an ignition feedstock we were wondering if there's a way to avoid having the version number in the feedstock name. Should we try here? |
fine for me too. Thanks Silvio |
Co-authored-by: Uwe L. Korn <[email protected]>
@xhochy provided the solution, it is just sufficient to specify the |
…bignition-sensors4/meta.yaml
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
…libignition-sensors4/conda_build_config.yml
Thanks @Tobias-Fischer @j-rivero , I added you as maintainers. |
I think the tests on windows should use if not exists ... exit 1 Happy to merge right after! |
Old habits die hard. : ) Done! I also tried to make the recipe quite parametric, so for future ignition libraries it should be sufficient to just copy the meta.yaml and change dependencies and initial metadata. |
- test -f ${PREFIX}/lib/libignition-{{ component_name }}{{ major_version }}.dylib # [osx] | ||
- test -f ${PREFIX}/lib/cmake/ignition-{{ component_name }}{{ major_version }}/ignition-{{ component_name }}{{ major_version }}-config.cmake # [not win] | ||
- if not exist %PREFIX%\\Library\\include\\ignition\\{{ component_name }}{{ major_version }}\\ignition\\{{ component_name }}.hh exit 1 # [win] | ||
- if not exist $PREFIX$\\Library\\lib\\ignition-{{ component_name }}{{ major_version }}.lib (exit 0) exit 1 # [win] |
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.
I think here is still a typo?
Instead of (exit 0) exit 1, it should just be (exit 1), right?
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.
Yes, fixed now, sorry for the noise.
After the changes the Windows existence checks are failing, not sure why. |
yeah the build log is really inconclusive :/ . Let me restart the windows build |
There is the same failure in #14323 that was copy pasted from this, so i guess there is some typo in the check, looking at it again. |
Found it, it was |
Related to #13551 . This adds a new missing library out of the ignition robotics libraries (see https://ignitionrobotics.org/).
The build on macOS is failing due to the need to 10.13 SDK, as done in #13677 we can merge the recipe and then re-render in the newly created feedstock.
I tried to put the recipe in theActually we modified the feedstock to specify explicitly its name, see #14313 (comment) .libignition-sensors
directory even if it creates alibignition-sensors4
package as given that we use a single feedstock to generate all the (different) packages namedlibignition-sensors<n>
we would like it to be calledlibignition-sensors-feedstock
instead oflibignition-sensors4-feedstock
(as in the future it will host alsolibignition-sensors5
,libignition-sensors5
, ...) but to be honest I am not sure it will work. However, this is just a nice to have, nothing really important.Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).