-
Notifications
You must be signed in to change notification settings - Fork 13
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
Export YarpTestCase and YarpFixtureManager as a library #1
Comments
Another possibility is to have a platform-dependent folder in the RTF. Some YARP specific plugins/macros, ... can go into that folder which can be optionally compiled ( |
@lornat75 which solution would you think would be best in the short term? |
I have to work on this for codyco-related testing, but we have to decide on which path to take... @lornat75 which option do you prefer ? |
The solution proposed by @apaikan seems good enough to me. |
👍 |
Done in #4 . |
For building test on external repository (for example codyco software or coman/walkman software), we need to expose the Yarp stuff.
We could create a yarp-tests library, given that this bits are iCub - indipendent, but probably requiring three different repos (
robot-testing
,yarp-tests
,icub-tests
) to be installed is an overkill, especially for users that don't use the superbuild.Another option is to simply add the cmake logic to export them as a library directly from this repo for the moment.
The text was updated successfully, but these errors were encountered: