Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add recipes for missing ignition libraries

See original GitHub issue

In few cases in the last months I had explain to interested users which ignition robotics libraries (a set of C++ libraries for robotics, see https://ignitionrobotics.org/) were still missing from conda-forge . As this info may be useful to anyone interested in this, especially for people interesting in adding the missing recipes, I think it is useful to report it and track it in this repo.

The Ignition libraries still not packaged in conda-forge are (see https://ignitionrobotics.org/libs for the complete list):

ignition-rendering done in https://github.com/conda-forge/staged-recipes/pull/13677, feedstock https://github.com/conda-forge/libignition-rendering4-feedstock
ignition-sensors fixed in https://github.com/conda-forge/staged-recipes/pull/14313
ignition-gui, depends on ignition-rendering, fixed in https://github.com/conda-forge/staged-recipes/pull/14323
ignition-gazebo, depends on ignition-gui, ignition-rendering and ignition-sensors, ongoing in https://github.com/conda-forge/staged-recipes/pull/14331 .
ignition-launch, depends on ignition-gazebo
ignition-utils (however, this is a new library that still needs to be released)

Note that the naming schema for Ignition libraries in conda forge is libignition-<library-name><major-version> .

cc @Tobias-Fischer @wolfv @mabelzhang @JShep1

Issue Analytics

State:
Created 3 years ago
Reactions:3
Comments:5 (4 by maintainers)

Top GitHub Comments

2reactions

traversarocommented, Jan 13, 2021

If you have any quick question, feel free also to pass by https://gitter.im/RoboStack/Lobby .

2reactions

traversarocommented, Jan 13, 2021

Do you have any advice for me for that PR (like things I may have done wrong or who I need to ping to get it in)? @traversaro

Hi @JShep1 , thanks for working on the recipe. My suggestion is to iterate on the PR until the CI passes, and if you have any doubt feel free to ping me, @Tobias-Fischer or @wolfv . Once the PR is ready, you will need someone with merge permissions. For C/C++ libraries you can ping the @conda-forge/help-c-cpp, and in practice for robotics-related library I typically ping also @wolfv that as part of the core conda-forge team can merge new recipes.