summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Add NEWLINE_STYLE option to configure_file (#3957)Peter Kuemmel2011-11-285-0/+38
|
* Merge topic 'fix-11213-vs10-mfc-support'David Cole2011-11-154-5/+39
|\ | | | | | | | | | | | | | | | | 537020f Tests: Nudge MFC test to pass on VS 6 dashboards (#11213) 51f442e VS11: Update InstallRequiredSystemLibraries.cmake for VS11 (#11213) d85ab7a Tests: Add environment logging to the MFC test (#11213) 011694c VS10: Use expected values for UseOfMfc (#11213) a2e6d24 Tests: Fix MFC test to work with VS 10 and later (#11213)
| * Tests: Nudge MFC test to pass on VS 6 dashboards (#11213)David Cole2011-11-093-5/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | InstallRequiredSystemLibraries does not install any dlls when used with VS 6 dashboards. Modify the ValidateBuild script to expect only 1 file when building with VS 6. Using "-DCMAKE_INSTALL_PREFIX=<INSTALL_DIR>" does not work when <INSTALL_DIR> evaluates to a long enough string. However, using "-DCMAKE_INSTALL_PREFIX:PATH=<INSTALL_DIR>" does work, even with the longer strings. So: make sure to include the ":PATH" when using this construct with ExternalProject calls so that they may install to the proper location on VS 6 builds. All existing calls that match "CMAKE_INSTALL_PREFIX.*INSTALL_DIR" include the ":PATH" after this commit. By the way: https://twitter.com/DLRdave/status/134339505397309440
| * Tests: Add environment logging to the MFC test (#11213)David Cole2011-11-081-0/+11
| | | | | | | | Simply to ease analyzing still-occurring dashboard failures.
| * Tests: Fix MFC test to work with VS 10 and later (#11213)David Cole2011-11-041-0/+15
| | | | | | | | | | | | | | | | | | | | | | The mfc app in the test was generated by the VS 7.1 wizard, and due to changes in VS since then, the values used for WINVER and _WIN32_WINNT caused compile errors when built with VS 10 or later. Change them to values appropriate for targeting Windows XP or later when building with VS 10 or later. See http://msdn.microsoft.com/en-us/library/6sehtctf.aspx for more info.
* | Merge topic 'add-mfc-test'David Cole2011-11-1528-0/+1778
|\ \ | |/ | | | | | | | | | | | | | | c71f7ab Tests: Avoid MFC test automatically for Watcom WMake builds (#11213) a42e3f2 Tests: Fix MFC test for old vs6 dashboards (#11213) b297da6 Tests: Fix MFC test w/ Make-based generators (#11213) 54595e6 Tests: Avoid MFC test automatically for VCExpress builds (#11213) 36b0c43 Tests: Add the MFC test (#11213)
| * Tests: Avoid MFC test automatically for Watcom WMake builds (#11213)David Cole2011-11-031-0/+10
| |
| * Tests: Fix MFC test for old vs6 dashboards (#11213)David Cole2011-11-031-1/+7
| | | | | | | | | | | | | | | | The MFC test's mfc1 directory was a "VS-MFC-wizard-generated" starter MFC app, using VS 7.1 as the generator. There's one define used in the generated rc file that was not available back in the VS6 days... Put a conditional define in here based on _MSC_VER to enable the test app to build on VS6 dashboards.
| * Tests: Fix MFC test w/ Make-based generators (#11213)David Cole2011-11-021-0/+12
| | | | | | | | | | An explicit add_definitions of _AFXDLL is required for shared library builds with non-Visual Studio generators.
| * Tests: Avoid MFC test automatically for VCExpress builds (#11213)David Cole2011-11-011-0/+24
| |
| * Tests: Add the MFC test (#11213)David Cole2011-11-0128-0/+1726
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Build a simple, do-nothing VS 7.1 MFC wizard generated app with CMake. Build it two different ways via ExternalProject, one with CMAKE_MFC_FLAG set to 1 for linking to MFC statically, and one with CMAKE_MFC_FLAG set to 2 for linking to the shared MFC dlls. Validate that the install tree of the static build has only one *.exe file in it and nothing else. Also validate that the install tree of the shared library build has multiple files in it (no less than 3) and that they are only of the expected types *.exe, *.dll and *.manifest. This commit does not address the issue reported in #11213, it merely adds a test that may be used to show that the bug report is valid. After this commit, the MFC test should fail on any dashboard machines that have MSVC defined, but cannot build an MFC app. We can then analyze that failure data as input to solving the issue.
* | Merge topic 'CPackRPM-perComponentHeader'David Cole2011-11-012-0/+2
|\ \ | | | | | | | | | | | | e20c59a CPackRPM support component specific variables for spec files
| * | CPackRPM support component specific variables for spec filesEric NOULARD2011-10-302-0/+2
| | | | | | | | | | | | | | | This is a modified version of a user patch Inspired-By: informant
* | | CTest: Look for CTestConfig.cmake in build dir first, then source dirJean-Christophe Fillion-Robin2011-10-275-0/+73
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Provide the ability to configure CTest with settings different from the ones available in the source tree by checking first if CTestConfig.cmake exists in the build tree. The motivation is to allow build system checking out external project to test and/or package them and submit the associated results to a different dashboard than the one specified (or not) in the source of the external project. For example, the build system of Slicer can checkout, build, test and package what I will call "extensions". These extensions can be developed by third parties who can test and submit to their own dashboard / project. When checked out by Slicer build system, the default dashboard can now be overwritten by adding a custom CTestConfig.cmake to the build directory. And if not overwritten, it would avoid to create CTestConfig.cmake within the source checkout of the extension.
* | Merge topic 'test-update-svn-1.7-issue-12535'David Cole2011-10-251-1/+11
|\ \ | | | | | | | | | | | | | | | 6d79b50 Teach CTest.UpdateSVN to detect svn add --depth before using it 74eb86c Fix CTest.UpdateSVN with Subversion 1.7 (#12535)
| * | Teach CTest.UpdateSVN to detect svn add --depth before using itBrad King2011-10-241-1/+11
| | | | | | | | | | | | | | | | | | Older svn versions do not have the --depth option for "svn add". Fortunately we do not need it for versions that old. Look for the option and use it only when available.
| * | Fix CTest.UpdateSVN with Subversion 1.7 (#12535)Brad King2011-10-241-1/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test adds a subdirectory with svn add subdir svn add ... subdir/foo.txt subdir/bar.txt Subversion 1.7 fails on the second command with svn: warning: W150002: '.../subdir/foo.txt' is already under version control svn: warning: W150002: '.../subdir/bar.txt' is already under version control svn: E200009: Could not add all targets because some targets don't exist because it considers adding an already-versioned file to be an error. Avoid the problem by using svn add --depth=empty subdir to add the subdirectory without the files it contains.
* | Add copyright noticesAlex Neundorf2011-10-222-0/+26
| | | | | | | | Alex
* | automoc:run moc on the header if the source file contains include "foo.moc"Alex Neundorf2011-10-224-1/+46
|/ | | | | | | | | | This fixes #12533. Before automoc did not check the header if the source file contained a statement, now it does. Additionally, moc is now only run on explicitely listed headers which contain a Q_OBJECT macro. Alex
* Silence make on OpenBSD in FindPackageModeTest(#12508)Alex Neundorf2011-10-121-0/+1
| | | | | | | | | | BSD make doesn't use -v for printing its name and version, and so complains on stderr that this is a bad command line option, used in Tests/FindPackageModeMakefileTest/CMakeLists.txt . Silence stderr to make that ugly output go away. Patch by David Coppy. Alex
* Build each library only once instead of once for each test.Stephen Kelly2011-10-094-5/+58
|
* Remove unused define.Stephen Kelly2011-10-091-8/+0
|
* Teach our tests about special cases for VS 11Brad King2011-09-233-3/+10
| | | | | | Teach the CheckCompilerRelatedVariables test to verify MSVC11. Update the special cases already in the Preprocess and VSExternalInclude tests for VS 10 to work for VS 11 too.
* Merge topic 'FortranCInterface-VS'David Cole2011-09-201-19/+26
|\ | | | | | | | | | | | | | | | | 67fcc83 Simplify IntelVSImplicitPath detection project a7ce26d Move IntelVSImplicitPath project to better location 539a822 Enable Fortran tests for IDE builds. 555f589 For VS Intel Fortran IDE builds, add a check to find the Fortran library PATH. 71402eb FortranCInterface: Compile separate Fortran lib in VerifyC[XX]
| * Enable Fortran tests for IDE builds.Bill Hoffman2011-09-091-19/+26
| |
* | Tests: Add the more modern Mac64 nightly buildDavid Cole2011-09-141-0/+2
| | | | | | | | | | We can remove the older ppc;i386 non-64-bit Mac nightly build in a little while after this one proves itself reliable.
* | Merge topic 'effective-platform-name'David Cole2011-09-1312-0/+1345
|\ \ | | | | | | | | | | | | | | | 64c9b31 Xcode: Add test to demonstrate iOS project in Xcode 59a2265 Xcode: Use EFFECTIVE_PLATFORM_NAME reference in ComputeOutputDir
| * | Xcode: Add test to demonstrate iOS project in XcodeDavid Cole2011-09-1212-0/+1345
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Presently, this test is only run manually because not all machines have an iOS SDK, complications associated with certificates and code signing, having a device attached, ... If you're setup to do iOS dev work, you can easily run this test manually on your Mac using the Xcode generator and run the result in the simulator or on your attached device.
* | | Merge topic 'add-kwstyle-test'David Cole2011-09-131-0/+13
|\ \ \ | | | | | | | | | | | | | | | | | | | | 3a0d632 KWStyle Test: Activate by default if KWStyle is found 91704ef Tests: Add a KWStyle test, equivalent to the make StyleCheck target
| * | | Tests: Add a KWStyle test, equivalent to the make StyleCheck targetDavid Cole2011-08-041-0/+13
| | | |
* | | | Merge topic 'fix-ctesttestcrash-test'David Cole2011-09-071-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 339a321 Tests: Look for "Illegal" or "SegFault" in the output
| * | | | Tests: Look for "Illegal" or "SegFault" in the outputDavid Cole2011-09-061-1/+1
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | One of the dashmacmini5 runs of this test results in an "Illegal exception" detected instead of a segfault. For the purposes of this test, we're going to say that either is a "crash."
* | | | Merge topic 'generate_export_header'David Cole2011-09-0710-0/+114
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | dbd776d Don't put what some compilers consider junk at the end of the line. 93d8d19 Add some more unit tests.
| * | | | Add some more unit tests.Stephen Kelly2011-09-0210-0/+114
| |/ / /
* | | | Merge topic 'fortran-format'David Cole2011-09-073-5/+9
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 90efed6 Xcode: Honor Fortran_FORMAT target and source file property 5c0c635 Fortran: Add support for free- and fixed-form flags 47a0c75 VS: Map Fortran free- and fixed-format flags to IDE options d6e2a06 VS: Map per-source Fortran flags to IDE options
| * | | Fortran: Add support for free- and fixed-form flagsBrad King2011-08-313-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Define a "Fortran_FORMAT" target and source file property. Initialize the target property from a "CMAKE_Fortran_FORMAT" variable. Interpret values "FIXED" and "FREE" to indicate the source file format. Append corresponding flags to the compiler command line.
* | | | Merge topic 'generate_export_header'David Cole2011-09-0120-0/+915
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6a6393c Don't use a variable name that might be used in other files. 5ca8c56 Fix up verbatim code sections of the dox. 75596e6 Don't start a line with a dash(-) 826374a Remove blank line at the start of the file. 8b9b8e1 Add documentation about the prefix and no_deprecated options. 51bc63a Fix the feature of using a specific prefix for macros. 3449f6b Add quotes in case cmake is installed in a prefix with a space. 36d28f2 Fix Compiler id variable name. 99b2aab Disable the tests for Watcom. 7ac0ab1 Quote paths in case there is a space in one of them. 89108b9 Look for errors reported by PGI too. e0cc024 Add missing NO_EXPORT macro variant. 1b031d1 More consistency in the macro options. 03d60c7 Try to make the macros do almost nothing for Watcom. 6adeda9 Possibly fix configuration test on AIX. e253348 Possibly fix test on HPUX. 32eff0c Test for too-old-intel compilers. 42154ec Fix up the regex command for Intel. a147a06 Add some settings for non-truncation of test output. bf73e75 Hopefully add version extraction for Intel. aa4f0b6 Fix the version extraction regex for clang. a493d1a Test the correct cxx variable. b6ee2ee Comment the test assertion for now a9a8b9e Exclude win32 from hidden visibility checks. afae7a9 Start testing expected values for compiler flags. 1ae3365 Exclude PGI from exports and deprecated. f426496 Exclude cygwin from the hidden visibility feature. f84c7db Don't enable deprecated on old GCC 9672b33 Don't enable deprecated on HP. 10d8c44 Disable testing of deprecated macros. 97392a7d Fixup forgotten part of aed84517c942a4c40f493fcf997cdf6a047349f8 2aeab4f Borland can't do deprecated. c41c68b Try to error on deprecated on Intel and SunCC. aed8451 Test for deprecated attribute before declspec. c448b09 Perform the -Werror test only once. fb88c6e Add some messaging output to make remaining issues findable. 01e9e98 Test -Werror instead of enabling it per compiler. 9aab2aa Expect the tests to pass if hidden visibilty is not enabled. 856bdb3 Don't change the expected build result based on the platform. df4615e Add the COMPILER_HAS_DEPRECATED only if it has a declspec variant 78a6e1c Exclude the XL compiler from the hidden-visibility test. e1f7ee3 Test for compiler features, instead of for specific platforms. 9554e10 Split the deprecated available check from setting macro values. 1590d5f Don't export methods on already exported classes. 750b67c Don't use hidden visibility on non-mingw windows either. 1f3be45 Make sure the hidden visibility variables never get set on MINGW. 399f415 Only set the deprecated attribute if hidden visibilty is enabled. 1c6b41b Remember to surround the other deprecated test in the Borland check. 3f7e036 Export deprecated free methods too. 7fa5592 Add some debug output to narrow down deprecation test issues 7924c1d Another attempt at fixing Borland. 50460ea Fix off-by-not in test for Borland. b443459 Use the correct project name compiletest not compilefail fc3772e Another attempt to fix the tests on Borland. bab4a22 Disable all export macros on Borland. cff9493 Only set the COMPILER_HAS_HIDDEN_VISIBILITY if GCC >= 4.2 af443b8 Set the CMAKE_RUNTIME_OUTPUT_DIRECTORY for windows builds. 61726f8 Only run the failure tests with gcc >= 4.2 002ddf2 Fix typo and tests failing as a result. 4443037 Fix tests with clang. ffaa127 Test expected no-op instead of aborting the build. 6aca0e2 Short-circuit the tests on unsupported compilers. d123bce Add some debug output. 3574b75 Simplify the compiler feature check c7a937b Simplify. We already know we have hidden visibility at this point. 3b188c8 Test for features, not specific compilers. 4718233 Remove the fatal_warnings option which is no longer used. b19911e Add missing licence header. 706ed2b Add a newline at the end of the file. 8963716 Add a newline at the end of the file. def0a54 Handle the case where the user changes the DEFINE_SYMBOL property. 3088070 Add the GenerateExportMacro with unit tests.
| * | | Fix Compiler id variable name.Stephen Kelly2011-08-241-1/+1
| | | |
| * | | Disable the tests for Watcom.Stephen Kelly2011-08-241-0/+15
| | | | | | | | | | | | | | | | They are timing out and showing up on the dashboard.
| * | | Quote paths in case there is a space in one of them.Stephen Kelly2011-08-241-3/+3
| | | |
| * | | Possibly fix test on HPUX.Stephen Kelly2011-08-231-1/+1
| | | |
| * | | Fix up the regex command for Intel.Stephen Kelly2011-08-181-1/+1
| | | |
| * | | Add some settings for non-truncation of test output.Stephen Kelly2011-08-171-0/+3
| | | |
| * | | Hopefully add version extraction for Intel.Stephen Kelly2011-08-171-0/+6
| | | |
| * | | Fix the version extraction regex for clang.Stephen Kelly2011-08-171-1/+1
| | | |
| * | | Test the correct cxx variable.Stephen Kelly2011-08-171-1/+1
| | | |
| * | | Comment the test assertion for nowStephen Kelly2011-08-171-1/+1
| | | | | | | | | | | | | | | | At least until I know which gcc versions do not pass.
| * | | Exclude win32 from hidden visibility checks.Stephen Kelly2011-08-171-1/+3
| | | |
| * | | Start testing expected values for compiler flags.Stephen Kelly2011-08-172-0/+65
| | | | | | | | | | | | | | | | | | | | Should help catch unhandled flag warnings so far not handled by check_cxx_compiler_flag FAIL_REGEXen.
| * | | Disable testing of deprecated macros.Stephen Kelly2011-08-143-19/+19
| | | | | | | | | | | | | | | | | | | | It is not possible to test for it sanely across multiple ancient compilers supported by cmake.
generated by cgit v0.12 at 2024-11-01 02:24:48 (GMT)