| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This creates a unit test for cmXMLSafe. See issue #10003.
|
|
|
|
| |
This creates a unit test for cm_utf8. See issue #10003.
|
|
|
|
|
| |
We create a new CMakeLibTests driver executable in which to writes unit
tests for CMakeLib. Our first test is a smoke-test of cmXMLParser.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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.
|
|
|
|
| |
Replaced with a pass regex.
|
| |
|
|
|
|
| |
executable, because it previously caused the outer ctest process to fail.
|
|
|
|
| |
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'...
|
|
|
|
| |
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.
|
|
|
|
|
| |
This platform configuration variable is unused. Modules are built using
the value of CMAKE_SHARED_LIBRARY_RUNTIME_${lang}_FLAG.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this test we start up a cmake script that runs a process that sleeps,
and the timeout for the script is shorter than the sleep time. However,
in order to properly detect that the sleeping grandchild is killed when
the script times out we need to give sufficient time for the script to
start the grandchild. Otherwise the log file for the grandchild is not
available.
On some (cygwin) builds our previous 1 second timeout for the script was
not long enough to let the interpreter load and start the grandchild.
We make the timeout time configurable by setting CTestTestTimeout_TIME
in the cache for CMake itself. It tells the test how long to let the
script run. The grandchild always sleeps for 4 seconds longer to ensure
a comfortable window during which the process tree can be killed.
|
|
|
|
|
| |
We remove from Tests/CTestTest*/CMakeLists.txt some historical cruft
that is no longer used by the test suite.
|
|
|
|
|
|
|
|
| |
This test requires that the dashboard script it drives be invoked with
"ctest -C <config> -S ...". We create a "CTestTest_CONFIG" variable to
hold a configuration selected at test time. We use the configuration
given to the outer CTest, if any, and then default to either Debug or
the CMAKE_BUILD_TYPE.
|
|
|
|
|
|
|
|
|
|
|
| |
We extend the CTestTestTimeout test to check that when a test times out
its children (grandchildren of ctest) are killed. Instead of running
the timeout executable directly, we run it through a cmake script that
redirects the timeout executable output to a file. A second test later
runs and verifies that the timeout executable was unable to complete and
write data to the log file. Only if the first inner test times out and
the second inner test passes (log is empty) does the CTestTestTimeout
test pass.
|
|
|
|
|
| |
The test_clean target is supposed to remove all test build directories.
We add the build directory for CMakeBuildTest because it was missing.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The commit "Fake $HOME to isolate tests from user" started setting $HOME
in the CTest script environment. On some platforms tests depend on some
local configuration in the home directory, such as the "cvs login" for
KWSys in CTestTest3.
In this commit we now construct a fake home dir during CMake config step
and populate it with a .cvspass file needed by the test. We also check
CTEST_NO_TEST_HOME to optionally disable the test home.
See issue #9949.
|
|
|
|
|
| |
We create a LinkDirectory test to check that the policy OLD and NEW
behaviors work as documented. See issue #9697.
|
|
|
|
|
|
|
|
|
|
| |
On platforms with $HOME in the environment, some of our features use it
to store information in the user home directory. However, tests for
these features should not touch the real user home directory. Instead
we configure a fake $HOME that points inside the build tree for use
during testing.
See issue #9949.
|
| |
|
|
|
|
|
|
|
| |
The commit "Fix get_filename_component ABSOLUTE mode" broke REALPATH
treatment of relative paths because it stopped storing the absolute path
in local variable 'filename'. This commit fixes the call to GetRealPath
to use the proper local variable and adds a test.
|
|
|
|
| |
at the Tests/CMakeLists.txt level.
|
|
|
|
| |
added test coverage for passing absolute paths to subdirs.
|
|
|
|
| |
overwritten.
|
| |
|
| |
|
|
|
|
| |
STRING(RANDOM or if given the new RANDOM_SEED argument. Add test and documentation of new argument.
|
|
|
|
| |
We add sample linker invocation lines for the GNU compiler on Mac.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some compilers use implicit link options of the form
-lcrt*.o
-lgcc*
-lSystem (on Mac)
-lSystemStubs (on Mac)
that provide system-wide symbols not specific to any language.
These need not be listed explicitly for mixed-language linking.
We teach CMake to remove the above items from the implicit library list
of each language. This change makes it possible to mix GNU compiler
versions in some cases.
|
|
|
|
|
| |
The find_package(<pkg>) command checks the <pkg>_DIR environment
variable. This commit documents and tests the feature.
|
|
|
|
| |
be done in parallel.
|
|
|
|
| |
currently causing the test to fail, still investigating the reason for this, will add coverage for it later)
|
|
|
|
|
|
| |
This allows for a built in bzip and zip capability, so external tools
will not be needed for these packagers. The cmake -E tar xf should be
able to handle all compression types now as well.
|
|
|
|
| |
[Cc]ouldn't and [Cc]ould not.
|
|
|
|
|
| |
This may help statistically detect implicit dependencies among unit
tests while running in parallel.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The commit "Test per-config OUTPUT_DIRECTORY properties" added this test
with a find_library() call in a CMake script, which requires an explicit
list of possible library prefixes and suffixes. This commit adds more
suffixes to match the libraries built on HP, MinGW, and Cygwin.
|
| |
|
|
|
|
| |
build on dashmacmini2 might have enough time to complete successfully. Use CMAKE_LONG_TEST_TIMEOUT instead of a hard-coded number for the test TIMEOUT property so that a calling script may adjust it by setting a higher CTEST_TEST_TIMEOUT value.
|
|
|
|
| |
build on dashmacmini2 might have enough time to complete successfully. Allow for up to 3 hours. After measuring successful runs for a few weeks, perhaps we can use a lower value.
|
|
|
|
| |
was installed on those machines to increase coverage. Do not add install rules with absolute paths when makensis is going to be used to build an installer.
|
| |
|
| |
|
|
|
|
|
|
|
| |
We test (ARCHIVE|LIBRARY|RUNTIME)_OUTPUT_DIRECTORY_<CONFIG> properties
by building COnly as a subdirectory and setting the properties to put
its files in specific locations. We build an executable that verifies
the targets actually appear where expected.
|
|
|
|
|
| |
This commit adds a CMake.ELF test to exercise cmELF and file(RPATH_*).
We test all combinations of 32/64-bit and LSB/MSB binaries.
|