You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note, this is probably my fault and of my requests in some old PRs. : )
I noticed that matlab-whole-body-simulator install slblocks.m in <install_prefix>/mex . While this is good as we don't need to add any more paths in the MATLAB path in the robotology-superbuild, it is not ideal as if somebody copies the structure of mwbs and uses it for its own library, the slblocks of the two libraries will be overwritten.
I just opened this as a note, we can discuss about this at the next meeting @nunoguedelha .
The text was updated successfully, but these errors were encountered:
Hi @traversaro , indeed I had this problem in mind. In immediate solution would be to move the mwbs_xxx.slx library files and the slblocks.m to a folder +mwbs/simulink, similarly to what is done in the whole-body-controllers library. There are other alternatives we can discuss in the meeting.
Note, this is probably my fault and of my requests in some old PRs. : )
I noticed that
matlab-whole-body-simulator
installslblocks.m
in<install_prefix>/mex
. While this is good as we don't need to add any more paths in the MATLAB path in the robotology-superbuild, it is not ideal as if somebody copies the structure ofmwbs
and uses it for its own library, theslblocks
of the two libraries will be overwritten.I just opened this as a note, we can discuss about this at the next meeting @nunoguedelha .
The text was updated successfully, but these errors were encountered: