Skip to content
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

Closed
traversaro opened this issue Mar 25, 2015 · 6 comments
Closed

Export YarpTestCase and YarpFixtureManager as a library #1

traversaro opened this issue Mar 25, 2015 · 6 comments

Comments

@traversaro
Copy link
Member

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.

@apaikan
Copy link
Contributor

apaikan commented Mar 27, 2015

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 (ENABLE_YARP) and exported by the RTF cmake packages. This can also solve robotology/robot-testing-framework#15 reported by @randaz81 .

@traversaro
Copy link
Member Author

@lornat75 which solution would you think would be best in the short term?

@traversaro
Copy link
Member Author

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 ?

@lornat75
Copy link
Member

The solution proposed by @apaikan seems good enough to me.

@traversaro
Copy link
Member Author

👍

@traversaro
Copy link
Member Author

Done in #4 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants