summaryrefslogtreecommitdiffstats
path: root/CTestCustom.cmake.in
Commit message (Collapse)AuthorAgeFilesLines
* Generators: remove KDevelop3 generatorAlex Neundorf2018-01-241-6/+0
| | | | | | | | | | The last KDevelop3 release was many years ago, in 2008 I think. I haven't seen or read about anybody using KDevelop 3 since a long time, so I think it can safely be removed from CMake. KDevelop 4 (first released in 2010) has its own proper CMake support now, independent from this generator. Alex
* CTestCustom: Suppress warning summary count from SunProBrad King2017-08-301-0/+1
| | | | | If warnings appear we want to match and/or suppress them independently. Always suppress the warning summary.
* CTestCustom: Generalize comment on warning summary suppressionBrad King2017-08-301-4/+3
|
* CTestCustom: Suppress exception loosening warningDaniel Pfeifer2017-08-261-0/+1
|
* CTestCustom: Suppress warning matched on source file nameBrad King2017-06-071-0/+1
| | | | | | | The `WarningMessagesDialog.cxx` source file name is displayed by MSVC in the compiler output, and the CTest launcher matches the name as a warning line starting in "Warning". Suppress this false positive with a custom exception.
* Regenerate lexer source codeDaniel Pfeifer2016-12-141-0/+4
| | | | | | | | Revise the manual procedure in the `*Lexer.in.l` files. Some of our post-processing steps are no longer necessary with the current set of supported compilers. Some steps changed with newer versions of flex. Then regenerate all lexers with flex version 2.6.1.
* Remove unused cm_sha2 infrastructureBrad King2016-11-101-2/+0
| | | | | All clients of `cm_sha2` have been ported to `cmCryptoHash`, which now uses librhash internally.
* CTestCustom: Suppress PGI IPA warningsBrad King2016-09-281-0/+1
|
* CTestCustom: Suppress PGI warnings in generated Lexer/Parser codeBrad King2016-09-261-0/+1
|
* CTestCustom: Suppress PGI compiler warning summary lineBrad King2016-09-261-0/+2
| | | | | We will match/ignore the actual warning lines, if any, so we can always ignore the summary line if present.
* CTestCustom: Suppress scan-build warnings in flex-generated lexerBrad King2016-09-081-0/+1
|
* CTestCustom: Suppress scan-build warnings in libuvBrad King2016-09-031-0/+3
| | | | | | | Clang scan-build warns in some expansions of RB_GENERATE_STATIC that it has a "Dereference of null pointer". It also warns that "The left operand of '==' is a garbage value" strangely. Simply suppress these since this is third-party code anyway.
* CTestCustom: Suppress scanbuild warning on unsigned left shiftBrad King2016-05-271-0/+1
| | | | | | | | | | | The Clang scanbuild tool warns: Utilities/cmliblzma/liblzma/simple/x86.c:106:23: warning: The result of the '<<' expression is undefined src = dest ^ ((1u << (32 - i * 8)) - 1); ~~~^~~~~~~~~~~~~~~ AFAIK overflow of a left shift on an unsigned type is well-defined.
* CTestCustom: Suppress warnings about rand() on OpenBSDBrad King2016-05-271-0/+1
| | | | | | We first suppressed this in commit v3.1.0-rc1~647^2 (CTestCustom: Suppress warnings about rand() and srand() on OpenBSD, 2014-04-12). Add another variant of the warning wording.
* CTestCustom: Suppress Windows manifest unrecognized element warningBrad King2016-05-271-1/+1
| | | | | | Our `cmake.version.manifest` file uses a "compatibility" element for Windows 10 support. Older MS tools warn about it being unknown, so suppress the warning.
* CTestCustom: Suppress -Wshadow warning about Solaris 'single' typedefBrad King2016-01-071-1/+2
| | | | | | | | | | On Solaris the system `/usr/include/floatingpoint.h` header contains typedef float single; so the GNU compiler warns that uses of the name `single` shadow it. Just suppress the warning because our uses of this name would become less readable with a different name.
* Port CMake from cmIML to KWIMLBrad King2015-12-181-1/+1
| | | | KWIML no longer uses a configured prefix.
* CTEST_CUSTOM_*: treat variables as listsBen Boeckel2015-09-211-11/+5
|
* VS: Windows Store/Phone package cert thumbprintGilles Khouzam2015-08-271-0/+1
| | | | | Add the PackageCertificateThumbprint property when there is a certificate on a WindowsStore or Phone app.
* CTestCustom: Ignore kwsys.testProcess-10 for MemCheck as KWSys doesBrad King2015-07-311-0/+4
| | | | | The test covers exceptional behavior that leaks memory, so ignore it for dynamic analysis runs.
* CTestCustom: Suppress HP-UX preprocessor concatenation warningBrad King2015-05-181-0/+1
| | | | | | | | | | | | | | | | | | | | The HP compiler on HP-UX 11.11 warns: Warning (anachronism) 823: ".../test_INT_format.h", line 194 # Redundant preprocessing concatenation operation results in two valid preprocessing tokens. Depending on this implementation defined behavior will result in non-portable code. TEST_C(INT32_C, -0x55000000, i32, int32_t, uint32_t) ^^^^^^ Warning (anachronism) 823: ".../test_INT_format.h", line 196 # Redundant preprocessing concatenation operation results in two valid preprocessing tokens. Depending on this implementation defined behavior will result in non-portable code. TEST_C(INT64_C, -0x5500000000000000, i64, int64_t, uint64_t) ^^^^^^ There is likely a subtle problem with the way one of the system-provided type macros is defined but the test passes despite the warning. Simply suppress it.
* CTestCustom: Suppress LNK4089 warning about RPCRT4Brad King2015-05-081-0/+1
|
* CTestCustom: Suppress LNK4089 warning about ole32Brad King2015-05-071-0/+1
|
* CTestCustom: Suppress more OS X universal binary link arch warningsBrad King2015-04-101-0/+1
|
* CTestCustom: Suppress more OS X universal binary link arch warningsBrad King2015-04-091-0/+1
|
* CTestCustom: Suppress OS X universal binary link arch warningsBrad King2015-03-311-0/+1
|
* Move scanbuild exceptions out of dashboard script and into cmake.Bill Hoffman2015-03-301-0/+12
|
* Merge topic 'openbsd-warnings'Brad King2014-04-151-0/+2
|\ | | | | | | | | f9f91fa8 CTestCustom: Suppress warnings about rand() and srand() on OpenBSD
| * CTestCustom: Suppress warnings about rand() and srand() on OpenBSDRolf Eike Beer2014-04-151-0/+2
| | | | | | | | | | We don't do crypto here, so a "poor" random doesn't matter. In fact we have API to allow people to get a repeatable sequence by setting a specific seed.
* | CTestCustom: Suppress -Wcast-align warnings in sha2 codeBrad King2014-04-111-0/+1
|/ | | | | This is third party code and we know that at run time the correct alignment is achieved.
* Merge topic 'suppress-conversion-warnings-in-QtWidgets'Brad King2014-04-031-1/+1
|\ | | | | | | | | 391c73db CTestCustom: Suppress conversion warnings in QtWidgets headers
| * CTestCustom: Suppress conversion warnings in QtWidgets headersBrad King2014-04-021-1/+1
| | | | | | | | We already do so for QtCore and QtGui headers.
* | CTestCustom: Suppress Clang "will never be executed" warnings in lexersBrad King2014-04-011-1/+1
|/ | | | Clang -Wunreachable-code-return warns on some generated lexer code.
* CTestCustom: Suppress "note: in expansion of macro" diagnostic contextBrad King2014-03-261-0/+1
| | | | | Such notes only appear with other diagnostics and should not be considered a warning on their own.
* CTestCustom: Suppress MIPSpro warnings about OlimitBrad King2014-03-061-0/+2
| | | | | | | | | Since we compile command implementations in large batches the translation units get too big for MIPSpro optimization limits. Suppress the warnings it produces: Warning: Olimit was exceeded on function ... Warning: To override Olimit for all functions in file, use -OPT:Olimit=3201
* CTestCustom: Suppress LNK4089 warning about SHELL32Brad King2014-01-021-0/+1
| | | | | | Add a warning suppression regex to match: LINK : warning LNK4089: all references to 'SHELL32.DLL' discarded by /OPT:REF
* Merge topic 'import-KWSys-subtree'Brad King2012-11-071-0/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 68579cd Merge branch 'upstream-kwsys' into import-KWSys-subtree cd83da9 KWSys 2012-11-05 (df32fa6f) 3517106 CTestCustom: Suppress LNK4089 warning about PSAPI 5c63fa3 Merge branch 'ctest-SUBMIT_INDEX-cdash' into import-KWSys-subtree 17fb60b Merge branch 'upstream-kwsys' into import-KWSys-subtree 7ae44db KWSys 2012-10-16 (b7a97ac3) 97c9887 pre-commit: Update KWSys rejection message for new workflow 3db0b51 KWSys: Submit dashboard builds to PublicDashboard 4b8d363 Merge branch 'upstream-kwsys' into import-KWSys-subtree a61f633 Merge branch 'master' into import-KWSys-subtree 8c55ea0 Merge branch 'upstream-kwsys' into import-KWSys-subtree 5d0de36 KWSys 2012-10-01 (bab53989) 7d3c295 KWSys 2012-05-02 (719638e2)
| * CTestCustom: Suppress LNK4089 warning about PSAPIBrad King2012-11-051-0/+1
| | | | | | | | | | | | Add a warning suppression regex to match: LINK : warning LNK4089: all references to 'PSAPI.DLL' discarded by /OPT:REF
* | Remove CMake-language block-end command argumentsKitware Robot2012-08-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ancient versions of CMake required else(), endif(), and similar block termination commands to have arguments matching the command starting the block. This is no longer the preferred style. Run the following shell code: for c in else endif endforeach endfunction endmacro endwhile; do echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | egrep -z -v 'Tests/CMakeTests/While-Endwhile-' | xargs -0 sed -i -f convert.sed && rm convert.sed
* | Convert CMake-language commands to lower caseKitware Robot2012-08-131-9/+9
|/ | | | | | | | | | | | | | | | | Ancient CMake versions required upper-case commands. Later command names became case-insensitive. Now the preferred style is lower-case. Run the following shell code: cmake --help-command-list | grep -v "cmake version" | while read c; do echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | xargs -0 sed -i -f convert.sed && rm convert.sed
* 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.