search

robotology / walking-teleoperation

Software related to walking and teleoperation.
BSD 3-Clause "New" or "Revised" License
30 stars 14 forks source link

Understand how to handle the installation of the applications for the different robots #126

Open S-Dafarra opened 1 year ago

S-Dafarra commented 1 year ago

Right now we install all the xml applications: https://github.com/robotology/walking-teleoperation/blob/3f5a30d7dd8ebed9d175aedcd1bb8b1789fbbef8/app/CMakeLists.txt#L28-L29

This ensures that the applications are always found. On the other hand, the applications are often robot dependent, and hence we are subject to cluttering.

We would need to understand how to improve this situation.

cc @GiulioRomualdi

S-Dafarra commented 1 year ago

Right now, we are not using yarp_configure_external_installation and hence the applications are installed in robotology-superbuild/build/install/share/yarp/applications/. I would like to understand how yarpmanager finds all the applications.

S-Dafarra commented 1 year ago

would like to understand how yarpmanager finds all the applications.

The applications path can be set from the file ymanager.ini by setting apppath.

Still, it is not clear to me yet how the applications are found in the YARP_DATA_DIRS

S-Dafarra commented 1 year ago

would like to understand how yarpmanager finds all the applications.

The applications path can be set from the file ymanager.ini by setting apppath.

Still, it is not clear to me yet how the applications are found in the YARP_DATA_DIRS

Interestingly, if apppath is not set, it is filled in automatically.

This is something we might exploit. In the default case all the apps are loaded. Then, for the robot setups, we might define a ymanager.ini file with only the subfolders of interest. Interestingly, load_subfolders is set to yes by default. Hence, it might be sufficient to properly organize the app in subfolders.