Compile examples in Travis builds

[jgvictores]

Many repos have examples that are compiled separately... that should not mean not having them tested via Travis!

---

• [x] yarp-devices
• [x] speech
• [x] kinematics-dynamics
• [x] tools
• [x] openrave-yarp-plugins

[PeterBowman]

We could have avoided https://github.com/roboticslab-uc3m/tools/issues/10#issuecomment-357375402 if examples were covered by tests.

Also, keep this in mind: roboticslab-uc3m/best-practices#21. Which boils down to: place Travis instructions that relate to building the examples in the before_script YAML section.

[PeterBowman]

Added TODO list to description.

[PeterBowman]

CMake alias targets may be useful here.

[PeterBowman]

Several examples are not even written in C/C++. Perhaps we could test bindings, too.

[PeterBowman]

Idea: add_subdirectory(examples) from root CMakeLists.txt, set ENABLE_examples=ON in Travis (defaults to OFF)?

[jgvictores]

IMHO:

1. CI is great, and it would be great to have examples at least compiled via Travis.
2. I'm happy with self-contained examples. If we add_subdirectory(examples), wouldn't it be catching repo-level dependencies rather than forcing them to be cited explicitly?

As a solution, maybe forcing Travis to enter examples and compile separately?

[PeterBowman]

ASWJ:

• Examples are going to remain as self-contained projects, no matter what.
• We could instruct root CMakeLists.txt to traverse these project so that everything is built together (main project + examples). However, this simple trick would force us to hide a few lines behind an if clause, for instance these find_package() instructions. Since we aim to illustrate best practices and usage of our libraries/APIs (targeted at devs), such hacks would be certainly misleading.
• Make Travis configure and compile the examples separately in the before_script section of .travis.yml.

[jgvictores]

@PeterBowman Thanks!!!