Hi Daniel,
and sorry all that I forgot to reply to the list,
On 15.02.2013 14:13, Daniel Stonier wrote:
Feel free to add a pointer to that script on the wiki where you
would expect it.
Indeed not all problems can be found that way, only some that would
fall through a normal catkin workspace build.
A more complete check tests for the following:
1.) Building a package together with a maximum amount of other
package in the same workspace with tests to check for cmake
namespace collisions.
2.) Build each package in isolation to test for missing cmake
dependencies
3.) Build and install each package in isolation and its declared
dependencies, and run tests to detect missing install dependencies
I do not know enough about pre-release tests to tell you what
happens there, I can only tell you what you can do locally.
cheers,
Thibault