[Insight-developers] Swig Wrapping Warnings.

[Lorensen, William E (Research)]

I think it is the cast-qual warning. We should not use this one in the
Wrapping directory. I'll verify this.

If this is the case, perhaps cmake can modify the flags for these platforms
in the wrapping directories.

Bill

-----Original Message-----
From: William A. Hoffman [mailto:billlist at nycap.rr.com]
Sent: Monday, April 19, 2004 11:49 AM
To: Lorensen, William E (Research); 'Brad King';
'hans-johnson at uiowa.edu'
Cc: 'itkdevel'
Subject: RE: [Insight-developers] Swig Wrapping Warnings.


What flags are you using Bill?

As far as I can see the default build should not produce tons of warnings.
The only one that is currently producing all the warnings is the uiowa
builds
that have extra flags like this:

-fstrict-aliasing   -Wall -Wcast-qual -Wstrict-prototypes 

The -Wall gcc, and -W3 on windows should not produce any warnings.
The problem is that the fixes for these things make the code not compile
with a "C" compiler so there is no chance that it can be incorporated back
into swig, and it makes merging with swig much more difficult to maintain
all the local warning changes.

-Bill



At 10:46 AM 4/19/2004, Lorensen, William E (Research) wrote:At 10:46 AM
4/19/2004, Lorensen, William E (Research) wrote:
>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
>_______________________________________________
>Insight-developers mailing list
>Insight-developers at itk.org
>http://www.itk.org/mailman/listinfo/insight-developers