<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Daniel,<br>
<br>
and sorry all that I forgot to reply to the list,<br>
<br>
On 15.02.2013 14:13, Daniel Stonier wrote:<br>
</div>
<blockquote
cite="mid:CAP6aRqb0KHG=fSxqZMSdQJ4SoSjbWYL_MSWARgovk6yBAuSE-w@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On 15 February 2013 18:49, Thibault
Kruse <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kruset@in.tum.de" target="_blank">kruset@in.tum.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Daniel,
<div class="im"><br>
<br>
On 15.02.2013 02:51, Daniel Stonier wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
These fails also happen in other ways - e.g. a missing
find_package(catkin REQUIRED ...) in just one package
in the stack also gets past pre-release.<br>
</blockquote>
<br>
</div>
There is a script called catkin_make_isolated that people
can use to build packages in isolation. This can help
detect certain missing declared dependencies. So
maintainers can make sure both catkin_make and
catkin_make_isolated pass locally before heading on to
pre-release.<br>
<br>
</blockquote>
<div><br>
</div>
<div style="">That's interesting - hadn't discovered that
tool before. Just did a quick run, and while it would
catch some issues, it would still not catch the install
dependency problems I outlined in the first email (unless
I manually sandboxed, cleared all the debs and reinstalled
individual package dependencies inbetween each isolated
build).</div>
</div>
</div>
</div>
</blockquote>
<br>
Feel free to add a pointer to that script on the wiki where you
would expect it. <br>
Indeed not all problems can be found that way, only some that would
fall through a normal catkin workspace build.<br>
A more complete check tests for the following:<br>
<br>
1.) Building a package together with a maximum amount of other
package in the same workspace with tests to check for cmake
namespace collisions.<br>
2.) Build each package in isolation to test for missing cmake
dependencies<br>
3.) Build and install each package in isolation and its declared
dependencies, and run tests to detect missing install dependencies<br>
<br>
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.<br>
<br>
cheers,<br>
Thibault<br>
</body>
</html>