That is great. <br><br>If I understand properly, that test make sure the building the install target works as expected. In addition to the component based install test that you proposed, it would also be great to validate the installed files can be successfully used to build a project. <br>
<br>If will also confirm that the installed ITKConfig.cmake behaves as expected. <br><br>Hth<br>Jc<br><br><div class="gmail_quote">On Wed, Apr 4, 2012 at 9:42 AM, Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 4/4/2012 9:11 AM, Jean-Christophe Fillion-Robin (Code Review) wrote:<br>
> A last question ... is how this gonna be tested in a systematic<br>
> way? Would be great, if a devel package could be generate and<br>
> the ITK applications build against it on a nightly basis.<br>
> To view, visit <a href="http://review.source.kitware.com/4873" target="_blank">http://review.source.kitware.<u></u>com/4873</a><br>
<br>
I run a nightly dashboard that builds all the tests as an outside<br>
project using an ITK install tree:<br>
<br>
<a href="http://open.cdash.org/buildSummary.php?buildid=2153144" target="_blank">http://open.cdash.org/<u></u>buildSummary.php?buildid=<u></u>2153144</a><br>
<br>
The installation is done by the Install test:<br>
<br>
<a href="http://itk.org/gitweb?p=ITK.git;a=tree;f=Utilities/InstallTest;hb=v4.1.0" target="_blank">http://itk.org/gitweb?p=ITK.<u></u>git;a=tree;f=Utilities/<u></u>InstallTest;hb=v4.1.0</a><br>
<br>
Currently it just installs everything without specifying any component.<br>
<br>
A second "InstallComponent" test could be added that installs things<br>
using one component at a time.<span class="HOEnZb"><font color="#888888"><br>
<br>
-Brad<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>+1 919 869 8849<br><br>