-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move yarprobotinterface logic to a standalone libYARP_robotinterface library #2168
Conversation
@drdanz there are a lot of failing tests for the licence check, any idea? It could be related to the -2020 in the headers?
|
Yes, the 2020 is not recognized yet, let me take care of that... |
A pointer to a TinyXML class is still used in the public API, but it will be removed in future refactor.
Right, I forgot... It's still failing because libraries are expected to be BSD. |
ec5629f
to
2d66c2a
Compare
Rebased and changed to BSD. |
acc0b06
to
37cf1e9
Compare
ok for changing the license! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR fixes the first part of #2005 . The possibility of attaching to device not opened by the
yarp::robotinterface::Robot
object will be added later.The following snippet show a basic use of the new
libYARP_robotinterface
library:There are the following open points, but I would prefer to get an early review on the modifications, so that this points can be addressed considering also the early review:All the open points have been addressedTests are missing (at least a basic test to run valgrind on the classes would be nice)Basic test for a library class added in ec5629fTheThis was fixed my making RobotInterfaceDTD a private header.RobotInterfaceDTD
class uses a TinyXML pointer as part of its public interface. At the moment there is no explicit dependency on the TinyXML thanks to the forward declaration added in 5403225, but in general to make the class actually usable from outside it would be great to avoid the use of TinyXML classes. If this is not possible, probably it would make sense to make theRobotInterfaceDTD
a non-public class, making its headers private.