Silvio Traversaro

cc @claudia-lat

@hu-yue and @GiulioRomualdi were the last two users tricked by this.

@GiulioRomualdi and @kouroshD were also affected by this. For the sake of finding this issue, the actual error that is printed by Visual Studio when executing the superbuild that it...

To avoid regressions such as https://github.com/robotology/robotology-superbuild/pull/534#issuecomment-733596206 .

At the moment, the installer do not officially support being installed in prefix different from `C:\robotology` , mainly due to YARP (related issues: https://github.com/robotology/yarp/issues/2445) and Gazebo (https://github.com/osrf/gazebo/issues/2782, https://github.com/osrf/gazebo/issues/2755) not being...

I renamed your issue to reflect the underlying problem, so that we have an issue in which to track this improvement.

Note that even if at the moment we do not support this explicitly, it should be possible to still use the binaries installed in `D:\robotology` with a few fixes: *...

> Maybe just using the installation prefix in the env variable script setup might solve the issue. 🤷‍♂️ Unfortunately that scripts is generate when the installer is generated, and so...

Most of the work necessary for this was done by @fiorisi in https://github.com/robotology/simmechanics-to-urdf/commit/a20ed5a6af87c1f85dd1bad69648f3ad9089468f .

I tried to provide the quickest possible solution in https://github.com/robotology/simmechanics-to-urdf/pull/59, but I did not checked even if the code runs. @HosameldinMohamed can you run the code and check if it...