summaryrefslogtreecommitdiffstats
path: root/CTestCustom.cmake.in
Commit message (Collapse)AuthorAgeFilesLines
* Suppress warnings occurring on the dashboards using the PGI compiler.David Cole2012-03-071-1/+2
|
* Merge topic 'suppress-clang-warning'David Cole2012-02-211-0/+1
|\ | | | | | | | | f4f94f3 CTestCustom: Suppress clang warning on the dashboard
| * CTestCustom: Suppress clang warning on the dashboardDavid Cole2012-02-161-0/+1
| | | | | | | | | | | | | | | | "argument unused during compilation" -- well, thanks, but ... If somebody has a fix to eliminate this warning entirely, rather than simply suppressing it from our dashboard results, I'm all ears.
* | Teach CTest what a ninja error looks like.Bill Hoffman2012-02-151-0/+4
|/ | | | | This will allow ninja dashboards to show ninja errors as well as compiler errors from the ninja build.
* CTestCustom.cmake: Ignore clang's summary warningDavid Cole2011-09-291-0/+4
| | | | Assuming prior text has matched some other warning expression...
* Suppress Qt warning for dashmacmini5 buildsDavid Cole2011-09-021-1/+1
| | | | | | | | The clang and icc compilers see two lines of warning with essentially the same message. But the second line does not say qglobal.h, so remove that part of the warning exclusion regex. See parent commit for further comments regarding this warning exclusion.
* Suppress Qt warning for dashmacmini5 buildsDavid Cole2011-09-011-0/+1
| | | | | | | | Qt 4.7 and earlier produce a "This version of Mac OS X is unsupported" warning on Lion, even though they work fine once built. We'll upgrade this machine to use Qt 4.8 when it's officially released. Until then, suppress this warning so that we don't miss other "more real" warnings on the dashboard.
* Xcode: Suppress same-old warning again.David Cole2011-08-231-0/+1
| | | | They changed the wording of it slightly with Xcode 4.
* Suppress erroneous warnings from Intel compilerDavid Cole2010-12-311-0/+1
| | | | | | | | | | | Googling for "warning #980: wrong number of actual arguments to intrinsic function" yields: http://software.intel.com/en-us/articles/cdiag980/ http://software.intel.com/en-us/articles/diagnostic-980-wrong-number-of-actual-arguments-to-intrinsic-function/ Since the compiler is at fault for issuing the warnings incorrectly, simply suppress them from CMake dashboard results.
* Suppress "loop was vectorized" "warnings."David Cole2010-11-081-0/+1
| | | | Eliminate appearance on dashboard results from Intel compilers.
* Suppress SGI MIPSpro warning 3968Brad King2010-06-091-1/+1
| | | | | | | | | | | | | | The warning appears everywhere we use static_cast to explicitly truncate an integer width. It appears in the form cc-3968 CC: WARNING File = ..., Line = ... implicit conversion of a 64-bit integral type to a smaller integral type (potential portability problem) static_cast<...>(...); ^ which is strange because a "static_cast" is not implicit. It also appears in system library code.
* Mask out warnings on ferrari dashboard.David Cole2010-06-081-0/+1
|
* Add more ignore stuff for OpenBSDBill Hoffman2010-05-141-1/+2
|
* Ignore OpenBSD warnings for use of strcpy, etc.Bill Hoffman2010-05-131-0/+1
|
* Expand the regular expression for ignoring xcode missing directories.Bill Hoffman2010-05-131-1/+1
|
* Exclude warnings for XcodeBill Hoffman2010-05-121-0/+1
|
* Add more excludes for the borland compiler.Bill Hoffman2010-04-271-0/+1
|
* Another pass at removing borland warnings.Bill Hoffman2010-04-261-11/+4
|
* Try to remove borland warnings again.Bill Hoffman2010-04-251-0/+5
|
* Coverage glob should search in Source dirZach Mullen2010-04-231-5/+0
|
* Implement extra coverage globbingZach Mullen2010-04-231-0/+5
|
* Exclude new warnings that showed up with ctest launcher.Bill Hoffman2010-04-061-0/+8
|
* exclude warnings from cmbzip2Bill Hoffman2009-11-141-0/+1
|
* get rid of the rest of the libarchive warnings by not seeing them..Bill Hoffman2009-11-131-1/+1
|
* Exclude Qt source files from coverage results.David Cole2009-10-241-0/+3
|
* Fix warnings in CMake source code. Suppress rampant warnings emanating from ↵David Cole2009-10-011-0/+1
| | | | Qt files.
* Fix warnings in CMake source code. Suppress warnings in Lexer and Parser ↵David Cole2009-09-301-0/+1
| | | | files that are 'too hard' to fix.
* COMP: Mask out shadowed declaration warnings that always follow already ↵David Cole2009-07-101-2/+3
| | | | masked Utilities/cmtar warnings.
* COMP: Suppress warnings from the Utilities/cmtar code in dashboard results.David Cole2009-07-081-0/+1
|
* ENH: Disable the xmlrpc drop method by defaultBrad King2009-06-111-1/+0
| | | | | | | We've chosen to drop our default dependence on xmlrpc. Thus we disable the corresponding CTest submission method and remove the sources for building xmlrpc locally. Users can re-enable the method by setting the CTEST_USE_XMLRPC option to use a system-installed xmlrpc library.
* COMP: Ignore warning LNK4204 for CMake dashboardBrad King2009-01-061-0/+1
| | | | | | | | This warning appears for libtar.obj, curltest.obj, and synch_client.obj regularly on CMake dashboard submissions from VS builds. They seem to occur due to some kind of race condition for objects in small targets. There is nothing wrong with the code, so this just suppresses the warnings.
* BUG: Exclude try_compile sources and kwsys files from CMake coverage results.David Cole2008-02-251-0/+11
|
* COMP: exclude some warnings on hpBill Hoffman2007-09-241-0/+1
|
* ENH: Avoid prompting for admin privileges when running CMakeSetup.exe on ↵David Cole2007-09-111-2/+1
| | | | Vista by adding a requestedExecutionLevel element to its manifest.
* ENH: Create CTestCustom.cmake instead of CTestCustom.ctest. Create the old ↵Brad King2007-08-311-0/+41
file to include the new one for compatibility. This should prevent the long delays of CTest traversing the whole tree looking for CTestCustom.ctest files.
generated by cgit v0.12 at 2024-12-28 12:42:15 (GMT)