summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* [0008668: CTest Dev: Missing executables shown as failed tests when using ↵Zach Mullen2009-12-105-20/+103
| | | | MPI.] Added a wrapping option to add_test so that exes built by the project can be safely wrapped in other exes and be listed as "not run" rather than "failed" if they are not built.
* New decision method to enable Fortran testsBrad King2009-12-103-17/+50
| | | | | | | | | | CMake does not enable Fortran for its own build, but it needs to find a Fortran compiler to know if it is possible to enable Fortran tests. Previously we searched for a hard-coded list of Fortran compilers which was duplicated from the CMakeDetermineFortranCompiler.cmake module. We now run CMake on a small test project that enables the Fortran language and reports the compiler it found. This represents a more realistic check of whether the Fortran tests will be able to find a compiler.
* Always use a configuration for CMake testsBrad King2009-12-101-15/+3
| | | | | | | | | | Previously our EnforceConfig script that loads at test-time would only enforce a non-empty CTEST_CONFIGURATION_TYPE for CMake 2.6.2 and lower. Now we simply always enforce use of a configuration, and select one of the configurations that was built if none is given. This is necessary to run tests like CMake.Install that need to know the configuration with which CMake was built.
* Test 'install' target of CMake itselfBrad King2009-12-103-0/+54
| | | | | | We create option CMake_TEST_INSTALL to enable a new CMake.Install test. It tests running the "make install" target to install CMake itself into a test directory. We enable the option by default for dashboard builds.
* Apply CMake test-time config to all testsBrad King2009-12-102-4/+4
| | | | | | We configure an EnforceConfig.cmake script to load at CTest time. Previously we loaded it from Tests/CTestTestfile.cmake, but now we load it from the top level so it applies to all tests.
* Fix memory leak that occurred when a test executable could not be started. ↵Zach Mullen2009-12-101-0/+1
| | | | (See BadExe test)
* Fix installation of CMake itselfBrad King2009-12-101-0/+7
| | | | | | | | | | | | | | | CMake 2.8.0 and below use the EXECUTABLE_OUTPUT_PATH setting from the top-level CMakeLists.txt file to compute the location of the "cmake" target for the special case of installing cmake over itself. The commit "Clean up CMake build tree 'bin' directory" moved the setting of EXECUTABLE_OUTPUT_PATH that affects the "cmake" target into the Source subdirectory. This broke the special-case lookup in the top level. We fix it by setting EXECUTABLE_OUTPUT_PATH at the end of the top-level CMakeLists.txt file. Now that we use add_subdirectory to process the subdirectories in order, this setting does not affect the subdirectories. Thus we fix installation while preserving the clean build tree 'bin' directory intended by the above-mentioned commit.
* Use add_subdirectory instead of subdirs in CMakeBrad King2009-12-101-11/+11
| | | | | | We switch CMake's own top-level CMakeLists.txt file to use the modern add_subdirectory() command instead of the old subdirs() command. This enables in-order processing.
* Simplify CMake self-install special caseBrad King2009-12-101-13/+4
| | | | | | | | | | CMake has a special case for the "make install" target when building CMake itself. We use the just-built CMake to install itself since an existing CMake installation cannot replace itself (at least on Windows). We simplify the code that computes the location of the CMake binary by taking advantage of existing generator support for target lookup. This will make it robust to any changes in CMake's own CMakeLists.txt files in the future.
* BUG: Fix bug #10,000.Clinton Stimpson2009-12-101-5/+13
| | | | | | Some fixes for including Qt frameworks. Remove extra "QtGui.framework" so its not Contents/Frameworks/QtGui.framework/QtGui.framwork/... anymore. Also include QtGui Resource folder, so a Cocoa/Qt based cmake-gui app works.
* KWSys Nightly Date StampKWSys Robot2009-12-101-1/+1
|
* Fix parallel HDF5 detection (#9982)Alexander Neundorf2009-12-091-1/+1
| | | | Alex
* Fix for bug 10001, make vs 10 compiler .rc files correctlyBill Hoffman2009-12-091-30/+39
|
* Create CMakeLibTests output dir for XcodeBrad King2009-12-091-0/+10
| | | | | | | | | Xcode 2.x forgets to create the target output directory before linking the individual architecture pieces of a universal binary for the target CMakeLibTests. Then it passes the directory to -L and -F options when linking the and warns that the directory does not exist. We work around the problem by using a pre-build rule on the target to create the output directory.
* KWSys Nightly Date StampKWSys Robot2009-12-091-1/+1
|
* Test XML encoding with UTF-8 character validationBrad King2009-12-082-0/+48
| | | | This creates a unit test for cmXMLSafe. See issue #10003.
* Test UTF-8 decodingBrad King2009-12-082-0/+126
| | | | This creates a unit test for cm_utf8. See issue #10003.
* CTest: Do not munge UTF-8 output in XML filesBrad King2009-12-084-34/+155
| | | | | | | | | | | | | CTest filters the output from tools and tests to ensure that the XML build/test result documents it generates have valid characters. Previously we just converted all non-ASCII bytes into XML-escaped Unicode characters of the corresponding index. This does not preserve tool output encoded in UTF-8. We now assume UTF-8 output from tools and implement decoding as specified in RFC 3629. Valid characters are preserved, possibly with XML escaping. Invalid byte sequences and characters are converted to human-readable hex values with distinguishing tags. See issue #10003.
* Create CMakeLib test driver and test cmXMLParserBrad King2009-12-085-0/+49
| | | | | We create a new CMakeLibTests driver executable in which to writes unit tests for CMakeLib. Our first test is a smoke-test of cmXMLParser.
* Clean up CMake build tree 'bin' directoryBrad King2009-12-083-6/+9
| | | | | | | | We re-arrange EXECUTABLE_OUTPUT_PATH settings to avoid putting utility and test executables in the 'bin' directory of the build tree. This makes the directory look like that in the installation tree, except that on multi-configuration generators we still use a per-config subdirectory.
* Remove useless include file filtersBrad King2009-12-084-7/+0
| | | | | | | | | | The commit "Cleanup regular expressions" removed real include filter expressions and replaced them with lines like INCLUDE_REGULAR_EXPRESSION("^.*$") that do no filtering. We simplify the change by removing the lines altogether.
* KWSys: Remove default exe output pathBrad King2009-12-081-7/+0
| | | | | | KWSys should not set variables outside its namespace. It can honor the EXECUTABLE_OUTPUT_PATH set by a host project, but tere is no need for it to set a default in the host project cache.
* Local test timeouts will now always take precedence over the global ↵Zach Mullen2009-12-081-2/+1
| | | | --timeout option.
* Remove unused DumpDocumentation codeBrad King2009-12-085-196/+0
| | | | | | | The DumpDocumentation executable and some supporting code and tests were completely unused by CMake. Generation of documentation is done by the individual executables with --help* options. In this commit we simply remove the unused code, executable, and test.
* Minor typo in commentsMathieu Malaterre2009-12-081-2/+2
|
* KWSys Nightly Date StampKWSys Robot2009-12-081-1/+1
|
* CMake global timeout (--timeout option) should prevail over individual test ↵Zach Mullen2009-12-071-1/+2
| | | | timeouts if it is lower than the individual timeout.
* Force CheckSourceTree test to pass if the source tree is not a CVS checkout. ↵David Cole2009-12-071-0/+11
| | | | The test can only do its checking if cvs is available and the source tree is a cvs checkout. Also, allow for the possibility that backslash characters exist in the HOME environment variable, because they may when built in a cygwin environment on Windows.
* Remove WILL_FAIL property from BadExe test, since CTest was returning 0. ↵Zach Mullen2009-12-071-1/+2
| | | | Replaced with a pass regex.
* Cosmetic changes to previous commit, for consistency.Zach Mullen2009-12-072-3/+2
|
* Added a unit test for running a test command which exists but is not an ↵Zach Mullen2009-12-076-1/+50
| | | | executable, because it previously caused the outer ctest process to fail.
* KWSys Nightly Date StampKWSys Robot2009-12-071-1/+1
|
* KWSys Nightly Date StampKWSys Robot2009-12-061-1/+1
|
* KWSys Nightly Date StampKWSys Robot2009-12-051-1/+1
|
* Turn off fortran as gnu fortran does not mix with vsBill Hoffman2009-12-041-0/+1
|
* Fix cvs password problems during the CMake.CheckSourceTree test. Make sure ↵David Cole2009-12-042-0/+15
| | | | cvs has access to the original value of the HOME environment variable and not the 'CMake testing' value of it so that any cvs passwords set up on the machine work to get the list of local modifications using 'cvs up'...
* Document usage of the include(CTest) moduleBrad King2009-12-041-9/+45
| | | | | | Previously this module gave only very brief documentation. We extend the module's documentation to describe CTestConfig.cmake, interaction with dashboard scripts, and the CTEST_USE_LAUNCHERS option.
* Fix issue #2336 - honor the -C arg to ctest. Honor it for all stages of ↵David Cole2009-12-0421-38/+603
| | | | running -D dashboards from the command line and running ctest_configure, ctest_build and ctest_test commands in -S scripts. Also, allow a script to change it by setting the CTEST_CONFIGURATION_TYPE variable: allows for multiple configuration build/test cycles within one script. Add a new signature for the cmake command build_command that accepts CONFIGURATION as one argument. The original build_command signature is still there, but now marked as deprecated in the documentation. Of course... also add CTestConfig tests to verify that -C is honored for -D dashboards and -S scripts.
* Remove GNU-specific flags from Linux.cmakeBrad King2009-12-044-7/+0
| | | | | | | | We remove the shared library compile/link flags "-fPIC" and "-shared" because they are not provided by all compilers on Linux. This allows us to drop code from the Linux-XL-*.cmake files that erases the bad flags. All other supported compilers already provide their correct flags for Linux in their own platform information files.
* Generalize support for Portland Group CompilerBrad King2009-12-048-15/+86
| | | | | | | | | | | | | | | We factor flags from Platform/Linux-PGI-Fortran.cmake into language independent helper modules Compiler/PGI.cmake Platform/Linux-PGI.cmake and invoke the macros from Compiler/PGI-<lang>.cmake Platform/Linux-PGI-<lang>.cmake This enables general support for the PGI compilers.
* Remove duplicate info from Linux SunPro info filesBrad King2009-12-043-6/+0
| | | | | The CMAKE_DL_LIBS variable is set platform-wide by Linux.cmake so we do not need to duplicate it in Linux-SunPro-<lang>.cmake files.
* Consolidate Linux Intel compiler informationBrad King2009-12-044-28/+38
| | | | | We consolidate duplicate code from Platform/Linux-Intel-<lang>.cmake files into a macro defined in Platform/Linux-Intel.cmake.
* Fix GNU C and Fortran flags on SunOSBrad King2009-12-042-1/+3
| | | | | | | | | | | The commit "Split GNU compiler information files" intended to move GNU flags from the platform-wide Platform/SunOS.cmake module into Platform/SunOS-GNU-<lang>.cmake using a helper module Platform/SunOS-GNU.cmake to consolidate flags. However, it accidentally put Fortran flags in the C language module and left out the Fortran module altogether. This fixes those mistakes.
* KWSys Nightly Date StampKWSys Robot2009-12-041-1/+1
|
* KWSys Nightly Date StampKWSys Robot2009-12-031-1/+1
|
* Move GNU flags from SunOS.cmake to SunOS-GNU.cmakeBrad King2009-12-022-17/+9
| | | | | The GNU-specific link-type flags do not belong in the platform-wide file.
* Hanle the case where a test can not be run because it is a bad executable.Bill Hoffman2009-12-022-15/+14
|
* Reduce duplication in Platform/<os>.cmake filesBrad King2009-12-0216-22/+16
| | | | | | | | | | | | | Several platform-wide linker flag variables are defined in Modules/Platform/<os>.cmake files for C and then copied by the Modules/CMake<lang>Information.cmake file for each language. We now use this approach for the variables CMAKE_EXE_EXPORTS_${lang}_FLAG CMAKE_SHARED_LIBRARY_SONAME_${lang}_FLAG CMAKE_SHARED_LIBRARY_CREATE_${lang}_FLAGS to avoid duplication for multiple languages in each platform file.
* Remove CMAKE_SHARED_MODULE_RUNTIME_${lang}_FLAGBrad King2009-12-026-30/+0
| | | | | This platform configuration variable is unused. Modules are built using the value of CMAKE_SHARED_LIBRARY_RUNTIME_${lang}_FLAG.
* Fix OS X dylib and module GNU flagsBrad King2009-12-024-0/+30
| | | | | | | | | | | The commit "Split GNU compiler information files" broke the settings of CMAKE_SHARED_LIBRARY_CREATE_${lang}_FLAGS CMAKE_SHARED_MODULE_CREATE_${lang}_FLAGS and started using just "-shared" for them. This worked when tested on newer Mac machines, but older ones really need "-dynamiclib" and "-bundle" (which are the documented flags anyway).
generated by cgit v0.12 at 2025-01-17 04:00:18 (GMT)