gazebo installation on Windows 11 (conda-forge) gazebo==11.14.0=*_10 unsuccessful #3379
Comments
|
Can you please report the output of:
Thanks! EDIT: for anyone looking for a quick solution, a known workaround is to install a version of gazebo compatible with boost 1.82.0, i.e.: |
|
Hi, I've run into the same issue while installing gazebo 11.14.0. conda list: set: But I've only faced this error intalling the latest version (11.14.0) and 11.13.0 runs fine! |
|
Thanks, I was able to reproduce the problem. |
|
The 0xc0000142 error means that some dll is not loaded, let's debug with https://github.com/lucasg/Dependencies . |
|
Not even |
traversaro
changed the title
|
Installing |
I do not see anything clearly wrong with that. I wonder if this problem is somehow related to robotology/gazebo-yarp-plugins#678 . |
|
The problem is present with all builds of libboost 1.84.0, so probably the problem is not related to some ABI break between different builds of libboost 1.84.0 . The problem is not present in Linux/macOS. |
|
Some updates: conda-forge/gazebo-feedstock#210 (comment) :
First problematic build: https://github.com/conda-forge/gazebo-feedstock/runs/23137603666, compiled with MSVC 19.38.33135.0 Ok, |
Note that this (i.e. the use of vs2022) does not explain by itself the problem, it is probably some sort of regression in the vs2022 version used in the CI. However, for sure this explains why a downstream vs2019 build failed, see robotology/gazebo-yarp-plugins#679 . |
For future reference: this was wrong. The dll not loaded/missing symbols error is 0xc0000135, 0xc0000142 is something like "application not starting correctly" or something similar. |
|
If indeed this has something to do with vs2022, you should now be able to rerender & rebuild the respective feedstocks, and hopefully the problem will then disappear. Sorry for the trouble! |
No problem! Indeed, I will open an issue to track the problem with vs2022, it is possible that just updating to a more recent version of vs2022 the problem disappears. Or let's hope that everyone stopped using gazebo classic and moved to gz-sim by the time that conda-forge migrates to vs2022. |
|
The problem should be fixed with the should work out of the box. Thanks a lot @aiswaryame94 and @ShadowDawg for reporting the problem, it was a tricky one. We also added tests in conda-forge/gazebo-feedstock#211 to avoid these kind of regressions. |
|
I got the same errors on all solutions stipulated including, conda create -n gazebo gazebo==11.14.0=*_9 conda create -n gazebo gazebo==11.14.0=orignameh160ba46_212 conda create -n gazebo gazebo==11.14.0=gzcompatnameh1a9e25f_12 Any update on a working gazebo classic distribution from conda-forge for Windows 11? I don't have problem with that in Windows 10, why Win 11 only? Many thanks! |
|
@USeebi can you open a new issue following the template? It is easier to track problems as new issue, as opposed to closed issues, thanks! |
Here are the steps I followed to install and run gazebo 11.14 on windows 11.
I get the following errors:
I also have paused the antivirus protection (Kaspersky), disabled windows firewall, toggled off the real-time protection on windows security. I also set gzserver.exe and gzclient.exe to use hig-processing NVIDIA graphics card, in the NVIDIA control panel.
I am still facing the same error. Could you kindly help me solve the same?
The text was updated successfully, but these errors were encountered: