It works in the VTK build tree...
What version of cmake/ctest?
What style dashboard scripts are you using?
How does your CONFIGURE_FILE for CTestCustom compare to the one found in
VTK's top level CMakeLists.txt?
Warnings are only suppressed when reported as part of a ctest driven
dashboard run. If you observe the actual build process using Visual Studio
or some flavor of make you will still see the warnings in the build
output...
HTH,
David
On 1/3/07, Kent Williams <[EMAIL PROTECTED]> wrote:
I added a CTestCustom.ctest file to my build directory as suggested on
the CMake website, and it doesn't appear to be doing what it is supposed
to.
I'll include my CTestCustom.ctest file below, but basically I want to
suppress warning messages that occur because of third party libraries
built outside our application. I used the CONFIGURE_FILE command to
copy it into the build directory.
Is this feature still kind of broken?
My CTestCustom.ctest file:
SET(CTEST_CUSTOM_WARNING_MATCH
${CTEST_CUSTOM_WARNING_MATCH}
"{standard input}:[0-9][0-9]*: Warning: "
)
SET(CTEST_CUSTOM_WARNING_EXCEPTION
${CTEST_CUSTOM_WARNING_EXCEPTION}
"Fl_Menu_Item\.H"
"FiberTrackingGUI\.cxx"
"has no symbols"
"itkConnectedComponentImageFilter\.txx(.*)comparison between signed
and unsigned"
"mac\.H(.*)deprecated"
"itkFixedArray\.h(.*)cast from"
"vxl(.*)support for exported templates is disabled"
)
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
