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
Former YARP device implementations of the IRobotManager class have been migrated to a new repository (asrob-uc3m/yarp-devices#1). This centralization efforts mean that we'll no longer want to maintain duplicates in src/libraries/RobotLib, namely:
YarpRobotManager is a dupe of RobotClient implemented as a static library (changes should be performed to handle a DL module now)
MockRobotManager should be transferred into a new YARP device
Aditionally, YCM will take care of the build automatization. Specifically, that single header (for now!) would be pulled and configured by YCM if not found on the system (according to YCM standards, we'll need a BuildASROB_YARP_DEVICES.cmake). We can take advantage from some ideas laid out at roboticslab-uc3m/questions-and-answers/issues/44 (interface targets).
The text was updated successfully, but these errors were encountered:
PeterBowman
changed the title
Refactor RobotLib with plugins, pull YARP network wrappers interfaces from new repo
Refactor RobotLib with plugins, pull YARP network wrapper interfaces from new repo
Jan 28, 2018
Mixing YCM with interface targets (in order to propagate the path to IRobotManager.h from asrob-uc3m/yarp-devices) was quite messy. I summed it up and left some hopefully useful pointers at roboticslab-uc3m/developer-manual#18 (comment).
Former YARP device implementations of the
IRobotManager
class have been migrated to a new repository (asrob-uc3m/yarp-devices#1). This centralization efforts mean that we'll no longer want to maintain duplicates in src/libraries/RobotLib, namely:IRobotManager.hpp
should disappear, all copies will be overhauled by IRobotManager.hpp@yarp-devicesYarpRobotManager
is a dupe ofRobotClient
implemented as a static library (changes should be performed to handle a DL module now)MockRobotManager
should be transferred into a new YARP deviceAditionally, YCM will take care of the build automatization. Specifically, that single header (for now!) would be pulled and configured by YCM if not found on the system (according to YCM standards, we'll need a
BuildASROB_YARP_DEVICES.cmake
). We can take advantage from some ideas laid out at roboticslab-uc3m/questions-and-answers/issues/44 (interface targets).The text was updated successfully, but these errors were encountered: