Open j-rivero opened 1 year ago
thanks for looking into this! Maybe we should just run with only either ogre 1.x or ogre 2.x on windows CI for now?
thanks for looking into this! Maybe we should just run with only either ogre 1.x or ogre 2.x on windows CI for now?
+1. Looking at vcpkg they don't support ogre1 and ogre-next together. Question is, which one should we choose?
my vote would be ogre-next as that's more commonly used and also the rendering default engine used in Gazebo
We have noticed that the ogre 2.2 plugin coming from the osrf vcpkg port repository is not being loaded in the Windows CI builds on build.o.o. The test ended up with an success result but the reality is that it won't run any test.
The Windows message probably from dlopen saying:
Is not really accurate since the module is that location. It is more interesting the message from gz-rendering that says:
gz-rendering is checking that the file exists and if it is not the case, the error message is different.
couldn't load library on path
probably means that it could not be loaded for other reason.My hypothesis for this first problem is https://github.com/osrf/vcpkg-ports/issues/12. In summary, the test is loading the Ogre 1.x dll instead of the Ogre 2.x dll so they can not be loaded. To support this, I run a build without Ogre 1.x in vcpkg, and after adding the vcpkg OGRE-2.2 bin directory I see the following:
The error probably comes from the fact of using the Remote Desktop Protocol or other problems with OpenGL but the dll loading seems to have been successful:
FYI: @iche033