-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Some embedded paths are not relocated on Windows #25
Comments
In particular the path |
Apparently a workaround is to set (see https://github.com/ignitionrobotics/ign-rendering/blob/fe9b5b3e1614f4f7ff3fb275a361d6de26d0fc6b/ogre/src/OgreRenderEngine.cc#L566):
By setting this env variables, the test is finally able to pass:
While we could just set these in the activation scripts, we would lose the feature of being able to install side by side different major version of ignition-rendering. Probably we should just check the point in which the paths are used, and add a workaround like the one in conda-forge/libignition-common-feedstock#36 where needed. |
As some of the problems seems to affect at least also macOS (see conda-forge/libignition-sensors-feedstock#17 (comment)), I think that perhaps just setting the env variables in the activation scripts is the least worst solution. Tryng to fix the binary relocation by reading conda/conda-build#1674 and conda/conda-build#2524 seems to be quite black magic (at least from what I understand of it right now) and that seems time that would be better spent by making properly relocatable (something like https://www.qt.io/blog/qt-is-relocatable) ignition-rendering upstream, that would benefit also other package managers that do not have "magic" binary relocation like conda (there was already some interest in this direction from people packaging ign-gazebo in conan, see gazebosim/gz-sim#626 for example). |
I am debugging some test failure on ign-sensors6, and they are failing with:
The text was updated successfully, but these errors were encountered: