Skip to content
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

Enable Python bindings #20

Closed
traversaro opened this issue Oct 3, 2021 · 4 comments
Closed

Enable Python bindings #20

traversaro opened this issue Oct 3, 2021 · 4 comments

Comments

@traversaro
Copy link
Contributor

There is an effort upstream to provide Python bindings. We should package them as well in conda-forge. Given that ign-math is one of the foundation (and also simples) ignition packages, we should pay attention on how we do this so that we can then replicate it in other ignition packages.

In particular, the easiest option is probably to just add python as a dependency (as I did for example in https://github.com/conda-forge/idyntree-feedstock/blob/0c58bf41cde4e7a50c9b97279b8e206b531b1ac8/recipe/meta.yaml) but in that case the lib** name would not have a lot of sense, and that may add a unwanted dependency on downstream C++ users. A more complex option would be to have split outpus between the C++ library and the Python bindings, but to be honest I never was able to fully grasped how to do that in the best way.

@traversaro
Copy link
Contributor Author

Related discussion in staged-recipes: conda-forge/staged-recipes#18234 (comment) .

@traversaro
Copy link
Contributor Author

I tried again to check some recipes that generate split packages for C++ and the related Python bindings, such as:

However, the logic is quite complex and I do not see enough benefit in having split packages that justify the additional mantainance effort. So, for now I will just enable the python dependency in the ignition packages that have Python bindings, then anyone interested is welcome to work in renaming the ignition library to remove the lib prefix or to produce split packages.

@traversaro traversaro mentioned this issue Apr 30, 2022
5 tasks
@traversaro
Copy link
Contributor Author

work in renaming the ignition library to remove the lib prefix

For that probably we can wait for the Ignition -> Gazebo renaming, whenever we rename the packages to gazebo- we can drop the lib prefix.

@traversaro
Copy link
Contributor Author

Fixed by #25 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant