robotology-superbuild

robotology-superbuild copied to clipboard

Document how to call blf Python bindings from MATLAB

2

An interesting use case is to call blf Python bindings from MATLAB, see https://github.com/dic-iit/bipedal-locomotion-framework/issues/53#issuecomment-789058776 . It could make sense to document/streamline the process of configuration of this workflow.

traversaro

Document and test in CI ROBOTOLOGY_USES_LUA option and update setup.sh

3

Once it is documented, we can remove the `mark_as_advanced`.

traversaro

https://github.com/robotology/robotology-superbuild/pull/749#issuecomment-845723343

traversaro

We should: * Add the option in https://github.com/robotology/robotology-superbuild/blob/master/.ci/all-options-enabled-cache.cmake and https://github.com/robotology/robotology-superbuild/blob/master/.ci/initial-cache.gh.cmake * Modify the logic in https://github.com/robotology/robotology-superbuild/blob/master/cmake/Buildgym-ignition.cmake to support the conda packages generation. In particular, we should not pass `${ROBOTOLOGY_SUPERBUILD_PYTHON_INSTALL_DIR}` as...

traversaro

Document how to handle the compilation from source if multiple MATLAB are found in the system

7

## Issue description After reinstalling the superbuild in a new folder and trying to use iDynTree bindings in MATLAB, I get the error: ``` >> iDynTree.StringVector() Invalid MEX-file '/Users/nunoguedelha/dev/PR-testing-2/robotology-superbuild/build/install/mex/iDynTreeMEX.mexmaci64': dlopen(/Users/nunoguedelha/dev/PR-testing-2/robotology-superbuild/build/install/mex/iDynTreeMEX.mexmaci64,...

nunoguedelha

See https://github.com/robotology/robotology-superbuild/commit/8f5e1129163104e94882faaa40d684b21c2d5f7d .

traversaro

Support installation of Windows binaries in an installation prefix different from C:\robotology

5

When installing using the windows installer on a drive different than C: some environment variables point to C nonetheless. In my case the installation was on D:\robotology and the environment...

Iaxama

Document YCM_EP_INSTALL_DIR

1

For users that use directly the robotology-superbuild, the fact that the robotology-superbuild install all its packages in `/install` is typically the desired behaviour and clear. However, for some specific use...

traversaro

Currently for some projects the Update Latest Releases is not able to update their tag, printing instead the message (see https://github.com/robotology/robotology-superbuild/runs/1755632387?check_suite_focus=true ): ~~~ fatal: No names found, cannot describe anything....

traversaro

Add a strict check for when using a releases that fails if a subproject does not have a <>_TAG variable set

1

traversaro