| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
When installing the main export file the install tree may be dirty. If
out-dated per-config files exist they may break the newly installed main
file which when it globs them. This teaches the installation script to
detect when it is about to replace the main export file with a different
one and cleans out any existing per-config files.
|
|
|
|
|
| |
This new command will be used by generated installation scripts to
determine whether an already-installed export file has changed.
|
|
|
|
|
|
| |
New method cmExportInstallFileGenerator::GetConfigImportFileGlob
computes the globbing expression that an installed export file uses to
load its per-configuration support files.
|
|
|
|
|
| |
This teaches CTest to send the test property "LABELS" in Test.xml
dashboard submissions as Label elements inside a Labels element.
|
| |
|
|
|
|
|
|
|
|
| |
This warning appears for libtar.obj, curltest.obj, and synch_client.obj
regularly on CMake dashboard submissions from VS builds. They seem to
occur due to some kind of race condition for objects in small targets.
There is nothing wrong with the code, so this just suppresses the
warnings.
|
|
|
|
|
|
|
| |
This moves management of the LC_MESSAGES environment variable into an
automatic variable. Previously if an error occurred the original
environment value was not restored. This makes the fix to issue #5936
more robust.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Previously we stored a vector of tests to preserve their order.
Property set/get operations would do a linear search for matching tests.
This uses a map to efficiently look up tests while keeping the original
order with a vector for test file generation.
|
|
|
|
|
| |
This fixes selection of a configuration when none is specified to find
an available configuration of the ctest test-command.
|
|
|
|
|
|
|
|
| |
When CTest detects that a test is running its own executable it
optimizes the test by using an internal instance of cmCTest instead of
creating a new process. However, the internal instance was using cout
and cerr directly. This redirects the output to a string stream to
avoid direct display of the internal test's output.
|
|
|
|
|
|
|
|
|
| |
When CMake 2.4 generates the build tree for CMake itself it asks the
built CMake to install itself using the rules that 2.4 generated. Since
the install rules use undocumented commands that are not compatible from
2.4 to 2.6 we need a special case to avoid failure. This sets a special
indicator variable in the install rules that enables a compatibility
hack to support the old install rule format.
|
|
|
|
|
|
| |
The internal file(INSTALL) command argument parsing used several
booleans with at most one set to true at a time to track argument
parsing state. This refactors it to use one enumeration.
|
|
|
|
|
|
| |
The get_target_property command contained some outdated documentation of
the LOCATION and TYPE properties. This removes it since they are now
documented in the properties list section of the documentation.
|
|
|
|
|
|
|
|
|
| |
Previously we left the LOCATION property undefined for imported targets
since it should no longer be used for non-imported targets. However, in
the case we do not know the name of an available imported configuration,
it is more readable to get the LOCATION property than LOCATION_<CONFIG>
for a bogus configuration <CONFIG>. This enables LOCATION for imported
targets and returns an unspecified available imported configuration.
|
| |
|
|
|
|
| |
Alex
|
| |
|
|
|
|
|
|
| |
The FATAL_ERROR to cmake_minimum_required is useful for projects that
require 2.6 to convince CMake 2.4 to error out. This clarifies its
usefulness in the documentation.
|
|
|
|
|
|
|
| |
When cmake_minimum_required is called with an unknown argument it should
not complain about it if the version specified is in the future. This
allows the proper error to be shown about the current CMake being too
old.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
pass -D arguments to the cmake configure step from a ctest -S script. Also clarify/correct some not so helpful error messages.
|
|
|
|
| |
followed by multiple calls to ENABLE_LANGUAGE. Use find_program to set the CMAKE_INSTALL_NAME_TOOL variable so it gets saved in the cache as a full path to the install_name_tool executable rather than a simple set which eventually goes out of scope.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When computing runtime search path ordering a constraint exists when a
file that may be found by the runtime search exists in a directory other
than that containing the desired file. We test whether a potential
conflict is really the same due to a symlink. Recently the change to
cmFindLibraryCommand to load directory content created a case in which
the same-file check would be incorrectly skipped. This avoids skipping
the check.
|
| |
|
| |
|
| |
|
|
|
|
| |
it properly by using the SYMBOLIC source file property to indicate to WMake when the sentinel file is not actually written by the update step.
|
|
|
|
| |
some cases to breakaway from tests without resetting to FALSE (BUG: 8188).
|
| |
|
|
|
|
| |
commands to fix the failing ExternalProject test on the CMake nightly dashboard.
|
| |
|
|
|
|
|
|
| |
svn and fix bug #8290
Alex
|
| |
|
| |
|
| |
|
|
|
|
| |
UPDATE_COMMAND handling. Output a -complete sentinel in synch with the -install sentinel, but do not list it as an OUTPUT of the custom command. That breaks the chaining of add_custom_commands between custom targets, but allows for a file-level dependency expression that will cause proper incremental rebuilds. When earlier targets rebuild, subsequent dependent targets will also rebuild. CVS and SVN update commands are always out-of-date so that they always run to get the latest source. To suppress that behavior on a per-external project basis use an explicit empty string for UPDATE_COMMAND. The source will still be checked out from the repository prior to the update step by the download step.
|
| |
|