Open pattacini opened 3 years ago
This should not be necessary since https://github.com/robotology/robotology-superbuild/pull/393 . In any case, a related issue is https://github.com/robotology/robot-testing-framework/issues/109 (earlier discussion: https://github.com/robotology/robotology-superbuild/issues/95).
Also this should be handled by setup.sh
, even if it would be indeed better if those files were installed, so that we could have the icub-tests work correctly even without assuming the existince of the source directory, as in the case of conda packages.
This should not be necessary since robotology/robotology-superbuild#393 . In any case, a related issue is robotology/robot-testing-framework#109 (earlier discussion: robotology/robotology-superbuild#95).
We need to expose plugins
here not just lib/rtf
. However, I could run further tests.
This should not be necessary since robotology/robotology-superbuild#393 . In any case, a related issue is robotology/robot-testing-framework#109 (earlier discussion: robotology/robotology-superbuild#95).
We need to expose
plugins
here not justlib/rtf
. However, I could run further tests.
You are right, I was confused!
We need to expose plugins here not just lib/rtf. However, I could run further tests.
maybe the setup.sh can set the LD_LIBRARY_PATH pointing where the icub-tests plugins are installed?
maybe the setup.sh can set the LD_LIBRARY_PATH pointing where the icub-tests plugins are installed?
I'm afraid they're not even installed.
My fault, the plugins are correctly installed in lib
so they're exposed via setup.sh
.
I didn't find the file .so within /usr/local/lib
in the first place.
What's left are the suites
.
Installing the project via
robotology-superbuild
made evident how it's not straightforward to launch a test.Take this docker recipe as an example, where the following points could be improved:
LD_LIBRARY_PATH
suites
are not installedcc @Nicogene @traversaro @mfussi66