-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Is run_exports/pin_subpackage with dart necessary? #107
Comments
So as far as I understand robotology/yarp.js#28 this is not an issue with gazebo which properly specifies the dartsim (and tbb etc) dependencies; see Instead in this particular case it's gazebo-yarp-plugins that does not have any dependencies on dartsim although it should have it (I'm not sure why that happens). So I think we can close the issue here?!? Or maybe I'm misunderstanding :) |
It is a bit hairy (and fortunatly a corner case), so mutual misunderstanding is quite possible. :D
The problem is that There is a similar issue for tbb, but in that case the actual classes that use tbb objects are limited and I could not find any downstream project that is using them, so I think we can relatively safely ignore the problem for tbb. |
Hm. You are probably right, but one more thing: why does the gazebo-yarp-plugins not depend on gazebo, which to my understanding would pull in all the other dependencies? It looks as if it just depends on yarp and libopencv. |
@traversaro - have you checked this further? |
I finally have an example of recipe that depends on Gazebo on conda-forge, see conda-forge/staged-recipes#21891 . This is failing with:
|
Related proposal: conda/ceps#77 . |
Based on the problem described in robotology/yarp.js#28 (comment), it seems that run_exports/pin_subpackage with dart is necessary as dart is exposed in the public headers of Gazebo. I am just opening this issue to remember this.
The text was updated successfully, but these errors were encountered: