summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Better CMake.ModulesNotice test regexBrad King2009-10-011-2/+3
| | | | | This commit updates the copyright notice regex to enforce a more strict format for contributor copyrights.
* New CMake.ModulesNotice test for copyright noticesBrad King2009-10-012-0/+46
| | | | This new test checks Modules/*.cmake for the required copyright notice.
* Improved safety and removed busy waiting from the CTestTestTimeout test.Zach Mullen2009-09-301-6/+11
|
* Test use of module .def files for MS toolsBrad King2009-09-299-0/+66
| | | | | | This adds a "ModuleDefinition" test enabled when using MSVC tools. It checks that .def files can be used to export .dll and .exe symbols and create corresponding .lib files that can be linked. See issue #9613.
* ENH: Added ctest test coverage for a test timeoutZach Mullen2009-09-295-2/+80
|
* Remove ctest_submit from CTestTestParallelZach Mullen2009-09-291-1/+0
|
* Test support for OLD behavior of policy CMP0002Brad King2009-09-284-0/+13
| | | | | | Policy CMP0002's OLD behavior allows duplicate non-custom targets. We test it with a project that builds two executables of the same name by setting CMP0002 to OLD.
* Oops. Last commit did not create subdir before doing a touch on a file in ↵David Cole2009-09-251-0/+1
| | | | it. So it fails on some platforms. This fixes that.
* Fix CMake Internal Error from cmTarget::GetOutputInfo - triggered by calling ↵David Cole2009-09-251-0/+27
| | | | GetLocation on a utility target - caused by custom command output file with same name as custom target. The fix is to avoid calling GetLocation unless the target is of a type that is expected to have a location...
* SEGFAULT does not work on watcom with ctest, so don't expect it to...Bill Hoffman2009-09-241-2/+8
|
* Use CTEST_TEST_GENERATORBill Hoffman2009-09-241-7/+6
|
* Make sure CTestTest scripts honor the CMAKE_TEST_GENERATOR so that if the ↵Bill Hoffman2009-09-243-21/+18
| | | | generator to build cmake is different than the one used for tests (watcom) is used.
* Visual Studio 10 has the same bug as 8 so make the path shorterBill Hoffman2009-09-231-2/+2
|
* Uncommented the dependency of CTestTestNoExe on CTestTestNoBuild so that it ↵Zach Mullen2009-09-231-1/+1
| | | | will work in parallel now.
* Make portable c for Parallel testZach Mullen2009-09-231-4/+4
|
* Add nightly builds for linux windows and mac.Bill Hoffman2009-09-231-12/+22
|
* Set new ctest tests to always run, whether CTEST_TEST_CTEST is enabled or ↵Zach Mullen2009-09-234-67/+66
| | | | not. Changed parallel test to be portable.
* CTestTestParallel now submits to public dashboard for easier debuggingZach Mullen2009-09-231-0/+1
|
* Teach Xcode generator to set XCODE_VERSIONBrad King2009-09-231-0/+1
| | | | | We set the variable 'XCODE_VERSION' in the CMake language to the Xcode version string (e.g. "3.1.2"). Platform config files may use it later.
* Added tests for ctest parallel options (PARALLEL_LEVEL, PROCESSORS, RUN_SERIAL)Zach Mullen2009-09-225-0/+93
|
* For the complex tests since they link to the CMake library make sure that ↵Bill Hoffman2009-09-211-0/+2
| | | | they are built with the type of build.
* Re-enabled failing tests; fixed ctest_build output to be consistent in the ↵Zach Mullen2009-09-211-17/+17
| | | | error condition across different make programs so that these tests would pass.
* Disable test as it fails on every system.Bill Hoffman2009-09-201-11/+11
|
* Disabling CTestTestNoBuild pending investigation of odd g++ output issues.Zach Mullen2009-09-181-7/+7
|
* Apparently, on FarAway the presence of errors during ctest_build does not ↵Zach Mullen2009-09-181-1/+2
| | | | cause the calling ctest to return an error condition.
* Cosmetic change to test CMakeListsZach Mullen2009-09-181-1/+1
|
* Added test coverage for ctest. Covers WILL_FAIL condition, tests that do ↵Zach Mullen2009-09-1810-0/+196
| | | | not build, tests that segfault, and test executable not found (bad command), as well as some pass and fail regular expressions.
* Fix CHECK_(C|CXX)_COMPILER_FLAG macro testBrad King2009-09-181-2/+2
| | | | | | The flag "-_this_is_not_a_flag_" was not rejected by GCC 4.0 on older Mac OS X. We now use "---_this_is_not_a_flag_" instead, which will hopefully be rejected by all compilers.
* Test CHECK_(C|CXX)_COMPILER_FLAG macrosBrad King2009-09-171-1/+9
| | | | | This teaches the TryCompile test to check that the compiler flag check macros correctly reject a bad flag. See issue #9516.
* Create CMake.ConfigureFile test for configure_fileBrad King2009-09-166-0/+28
| | | | | This test checks that configure_file() handles input and output file arguments as documented.
* Factor out CMake.File test result check for re-useBrad King2009-09-162-35/+40
| | | | | | | The CMake.File test runs several scripts through "cmake -P" and checks the output and result against known good values. This commit factors out the checking code into a separate CMakeCheckTest module. The module may be used by new tests.
* Test add_subdirectory inside functionBrad King2009-09-161-0/+35
| | | | | | | This commit teaches the FunctionTest to check variable scope behavior when a subdirectory is added inside a function call. Any PARENT_SCOPE sets in the subdirectory should affect only the function scope which called add_subdirectory and not its parent scope.
* Test that CTest can handle missing newlinesBrad King2009-09-111-0/+4
| | | | | We create test 'CTest.NoNewline' to print output with no newline. This tests CTest's ability to handle a missing newline.
* Enable C and C++ first in Fortran testBrad King2009-09-091-1/+1
| | | | | | CMake now looks for a Fortran compiler matching any C or C++ compiler already enabled. We test this by enabling C and C++ first in the Fortran test, which is what user projects will likely do.
* Use more verbose/descriptive names for the "public API" functions in the ↵David Cole2009-09-081-21/+29
| | | | ExternalProject.cmake module. Follow the cmake function naming convention, using a ModuleFileName_ prefix. Locate stamp files under a CMAKE_CFG_INTDIR subdir of the stamp dir so that debug and release builds have separate stamp files for Visual Studio builds. If no CMAKE_GENERATOR argument is given to ExternalProject_Add, default to using the parent project's cmake generator.
* Put custom commands in topological order for VS 10Brad King2009-09-071-9/+0
| | | | | | | | | | | | | | | | Visual Studio 10 uses MSBuild to drive the build. Custom commands appear in MSBuild files inside CustomBuild elements, which appear inside ItemGroup elements. The Outputs and AdditionalInputs elements of each CustomBuild element are evaluated according to timestamps on disk. MSBuild does not use inputs/outputs to order CustomBuild steps within a single ItemGroup or across multiple ItemGroup elements. Instead we must put only unrelated CustomBuild elements in a single ItemGroup and order the item groups from top to bottom using a topological order of the custom command dependency graph. This fixes CustomCommand and ExternalProject test failures, so we remove the expectation of these failures.
* Add a test for FILE(READ ... HEX) together with a tiny binary file.Alexander Neundorf2009-09-062-0/+9
| | | | Alex
* Add test step to ExternalProject builds. Rename SVN_TAG to SVN_REVISION ↵David Cole2009-09-031-4/+13
| | | | since it is a more accurate name.
* ENH: Added PARALLEL_LEVEL option for ctest_memcheck(). Added PROCESSORS ↵Zach Mullen2009-09-031-2/+2
| | | | option to set_tests_properties (implementation to come).
* Make CTest.UpdateGIT robust to user git configBrad King2009-09-011-0/+7
| | | | | | | Part of this test does "git pull" on a dirty work tree. We need to make sure that 'branch.master.rebase' is false for the test repository. Otherwise if it is true in the user configuration then pull will refuse to rebase and the test will fail.
* Test the user package registryBrad King2009-09-015-0/+33
| | | | | | We teach the FindPackageTest to build a sample project that stores its build tree in the user package registry using export(PACKAGE), and then find it with find_package.
* Test link multiplicity export/importBrad King2009-09-019-1/+26
| | | | | | | We test that LINK_INTERFACE_MULTIPLICITY propagates through export() and install(EXPORT) into dependent projects. A simple cycle of two archives that need to be scanned three times ensures that the importing project uses the multiplicity correctly.
* Test link multiplicityBrad King2009-09-015-4/+11
| | | | | This tests the LINK_INTERFACE_MULTIPLICITY property for a cycle of three static libraries that must be scanned three times to link properly.
* Added ctest -N test. Fixed ctest working directory bug. MemCheck fix ↵Zach Mullen2009-08-281-0/+3
| | | | coming soon...
* Enforce FortranCInterface_VERIFY in Fortran testBrad King2009-08-241-2/+2
| | | | | This removes the QUIET option from FortranCInterface_VERIFY in the Fortran test to really test the detected interface everywhere.
* Create FortranCInterface_VERIFY functionBrad King2009-08-241-0/+2
| | | | | | | This function builds a simple test project using a combination of Fortran and C (and optionally C++) to verify that the compilers are compatible. The idea is to help projects report very early to users that the compilers specified cannot mix languages.
* Output command that failed, if it fails.Bill Hoffman2009-08-121-1/+2
|
* Test add_test() generator expressionsBrad King2009-08-116-0/+96
| | | | | | | This teaches the 'testing' test to try generator expressions in arguments to add_test(NAME). This test case mimics a common use-case of passing executables to test driver scripts. We excercise the syntax for per-configuration target file names.
* Rewrite FortranCInterface moduleBrad King2009-08-052-36/+38
| | | | | | | | | | | | | | | | | | | | This is a new FortranCInterface.cmake module to replace the previous prototype. All module support files lie in a FortranCInterface directory next to it. This module uses a new approach to detect Fortran symbol mangling. We build a single test project which defines symbols in a Fortran library (one per object-file) and calls them from a Fortran executable. The executable links to a C library which defines symbols encoding all known manglings (one per object-file). The C library falls back to the Fortran library for symbols it cannot provide. Therefore the executable will always link, but prefers the C-implemented symbols when they match. These symbols store string literals of the form INFO:symbol[<name>] so we can parse them out of the executable. This module also provides a simpler interface. It always detects the mangling as soon as it is included. A single macro is provided to generate mangling macros and optionally pre-mangled symbols.
* Remove WXDialog source codeBrad King2009-08-053-106/+0
| | | | | The QtDialog is our supported cross-platform GUI, so the WXDialog source is no longer needed.
generated by cgit v0.12 at 2025-01-04 06:52:55 (GMT)