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
We have some *.py.cmake files. I think this could easily be avoided, and should be. Plus it is currently broken because of a typo.
I can handle katana_holding.py.cmake, but for appli-test-simple-seq-play.py.cmake, there is also a appli-test-simple-seq-play.py available. @olivier-stasse : can you confirm that I can remove appli-test-simple-seq-play.py.cmake as appli-test-simple-seq-play.py seems to be more recent and used instead ?
The text was updated successfully, but these errors were encountered:
Thanks for picking this up.
appli-test-simple-seq-play.py should not be used as it has hardcoded path value.
This a left over of tests.
The problem is to find where on the robot the files are located.
rospack would be the easiest way to handle the issue.
Thanks for your answer. But I would like to avoid rospack, as I don't see the need for ROS to find paths to files. Moreover, rospack doesn't work on 16.04.
To address the issue of hardcoded path, we can either use CMake, or a strategy similar to stack-of-tasks/talos_integration_tests#6
Hi,
We have some
*.py.cmake
files. I think this could easily be avoided, and should be. Plus it is currently broken because of a typo.I can handle
katana_holding.py.cmake
, but forappli-test-simple-seq-play.py.cmake
, there is also aappli-test-simple-seq-play.py
available. @olivier-stasse : can you confirm that I can removeappli-test-simple-seq-play.py.cmake
asappli-test-simple-seq-play.py
seems to be more recent and used instead ?The text was updated successfully, but these errors were encountered: