[vtk-developers] Guidance needed fixing problems doing 64bit compile on Mac OS X

[David Cole]

It's always best to eliminate warnings at their source. (If you don't,
they'll eventually come back again later...)

For "3rd party" warnings in VTK, it's probably best to update to a newer
version of that code base if there's one that eliminates those warnings and
is stable enough for general use. Making that assessment is usually the hard
part, especially given the wide variety of platforms/compilers VTK covers.

If warnings can't be eliminated like that, consider eliminating them in
VTK's copy of the source. Then nobody has to see them anymore, but they
might come back later if we do update to a newer version of that lib.

Lastly, warnings can be masked out of dashboard results, via
VTK/CMake/CTestCustom.ctest.in, but we try to do that only when there's no
other option. Because even if you mask them out like that, folks building
interactively are still going to see those warnings.

Helpful? I hope...
David

On 1/26/07, Sean McBride <sean at rogue-research.com> wrote:
>
> On 2007-01-26 06:30, David Cole said:
>
> >Turns out that the test you're having a problem with is dependent on
> >VTK_USE_INFOVIS being ON, but the test was added unconditionally in the
> >CMakeLists file...
> >
> >I just committed the fix, along with a "missing Tk libraries on the link
> >line when VTK_USE_RENDERING is OFF" issue that I accidentally discovered
> >while investigating.
> >
> >/cvsroot/VTK/VTK/IO/Testing/Cxx/CMakeLists.txt,v  <--  CMakeLists.txt
> >new revision: 1.26; previous revision: 1.25
> >/cvsroot/VTK/VTK/Wrapping/Tcl/CMakeLists.txt,v  <--  CMakeLists.txt
> >new revision: 1.66; previous revision: 1.65
> >
> >Update from CVS and try again with your same settings. It should work
> now.
>
> You rock David!  It works.  And 100% of the tests pass.  Of course,
> there are only 39 tests in such a limited build of vtk. :) Still, it is
> impressive.  I will set up a dashboard for this config.
>
> There are some compiler warnings in some 3rd party code (libtiff,
> freetype, etc.).  What is kitware's policy here?  Better to fix the
> warnings upstream and update vtk to the newest code, or fix the warnings
> in vtk's copy and have a fork of the code? or...?
>
> --
> ____________________________________________________________
> Sean McBride, B. Eng                 sean at rogue-research.com
> Rogue Research                        www.rogue-research.com
> Mac Software Developer              Montréal, Québec, Canada
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20070126/559e7b1c/attachment.html>