[Insight-developers] Testing ITK installation components (was: ENH: Enable component-based packaging.)

[Jean-Christophe Fillion-Robin]

That is great.

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.

If will also confirm that the installed ITKConfig.cmake behaves as
expected.

Hth
Jc

On Wed, Apr 4, 2012 at 9:42 AM, Brad King <brad.king at kitware.com> wrote:

> On 4/4/2012 9:11 AM, Jean-Christophe Fillion-Robin (Code Review) wrote:
> > A last question ... is how this gonna be tested in a systematic
> > way? Would be great, if a devel package could be generate and
> > the ITK applications build against it on a nightly basis.
> > To view, visit http://review.source.kitware.**com/4873<http://review.source.kitware.com/4873>
>
> I run a nightly dashboard that builds all the tests as an outside
> project using an ITK install tree:
>
>  http://open.cdash.org/**buildSummary.php?buildid=**2153144<http://open.cdash.org/buildSummary.php?buildid=2153144>
>
> The installation is done by the Install test:
>
>  http://itk.org/gitweb?p=ITK.**git;a=tree;f=Utilities/**
> InstallTest;hb=v4.1.0<http://itk.org/gitweb?p=ITK.git;a=tree;f=Utilities/InstallTest;hb=v4.1.0>
>
> Currently it just installs everything without specifying any component.
>
> A second "InstallComponent" test could be added that installs things
> using one component at a time.
>
> -Brad
>



-- 
+1 919 869 8849
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-developers/attachments/20120404/a39764f9/attachment.htm>