[Insight-developers] Swig Wrapping Warnings.

[Lorensen, William E (Research)]

I don't think exceptions are the way to go. Dart (or ctest) warnings should
be a last resort. When I do my compiles interactively, I get thousands of
warnings that are wrapping related. Maybe we can turn off those particular
warnings when in the Wrapping tree.

I'll look into it.

Bill

-----Original Message-----
From: Brad King [mailto:brad.king at kitware.com]
Sent: Monday, April 19, 2004 10:19 AM
To: hans-johnson at uiowa.edu
Cc: William A. Hoffman; itkdevel
Subject: Re: [Insight-developers] Swig Wrapping Warnings.


Brad King wrote:
> William A. Hoffman wrote:
> 
>> Perhaps we can add some cmake stuff to downgrade the warnings
>> just for the Wrapping part of the dashboard.   
> 
> 
> One other problem is that because of the templates, many ITK classes are 
> not compiled except for during wrapping.  Shutting off wrapping warnings 
> would also disable ITK warnings.  Perhaps instead we should setup 
> warning blockers for Dart that do not report warnings in the generated 
> source files themselves.

Adding these warning blockers will be extremely ITK-specific.  We should 
probably not add them to the Dart list of exceptions.  CMake 2.0 will 
come with a ctest feature that allows per-project exceptions (it already 
works in the CVS version).  If this dashboard were submitted using ctest 
instead of the Tcl-based Dart client, then we should be able to add the 
exceptions.

-Brad
_______________________________________________
Insight-developers mailing list
Insight-developers at itk.org
http://www.itk.org/mailman/listinfo/insight-developers