| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
We now search in
<prefix>/<name>*/
<prefix>/<name>*/(cmake|CMake)
when looking for package configuration files. This is useful on Windows
since the Program Files folder is in CMAKE_SYSTEM_PREFIX_PATH. These
paths are the Windows equivalent to the Apple convention application and
framework paths we already search. See issue #8264.
|
|
|
|
|
|
| |
On 64-bit Windows there may be two Program Files folders, one for 32-bit
binaries and one for 64-bit binaries. When we compute
CMAKE_SYSTEM_PREFIX_PATH we should put both folders in the path.
|
|
|
|
|
|
| |
The $ENV{VAR} syntax permits access to environment variables. This
teaches CMake to recognize most characters in the VAR name since some
environments may have variables with non-C-identifier characters.
|
| |
|
| |
|
|
|
|
|
|
|
| |
For bug #7191.
Improvements to the dialog that sets up the first configure.
Fixing the large size of it by breaking it up into a wizard.
Also incorporated suggestions from bug report.
|
|
|
|
|
|
|
| |
When the find_package command loads a <name>-version.cmake file to test
the package version it must prevent the version file from affecting
policy settings. Therefore the policy settings must be pushed and
popped.
|
|
|
|
|
|
|
| |
Generated cmake_install.cmake script code used MATCHES to compare
component names. This does not support characters considered special by
regular expression syntax in component names. This change uses STREQUAL
instead. See issue #8256.
|
|
|
|
|
|
| |
When an object file directory is too deep to place an object file
without exceeding CMAKE_OBJECT_PATH_MAX, this issues a warning.
Previously we silently ignored the problem. See issue #7860.
|
|
|
|
|
|
| |
When computing the maximum length full path to the build directory under
which object files will be placed, pass the actual path instead of just
its length. This will be useful for error message generation.
|
|
|
|
|
|
|
|
| |
The previous change to test finding in lib/cmake/<name>* weakened the
versioned find tests. Since the lib/cmake paths are searched before
lib/<name>* paths the previous change skipped requiring the command to
ignore zot-3.0 when finding zot-3.1. This change restores that and adds
zot-4.0 to test the lib/cmake path.
|
| |
|
|
|
|
|
| |
Add QT_TRANSLATIONS_DIR pointing to the Qt translation files, and docs for it.
Also add docs for QT_BINARY_DIR.
|
| |
|
|
|
|
|
|
|
|
| |
The CMAKE_<CONFIG>_POSTFIX variable and <CONFIG>_POSTFIX property were
not documented. This updates the CMAKE_DEBUG_POSTFIX and DEBUG_POSTFIX
documentation to refer to the more general variable/property. It also
clarifies that the variable is used as the property default only for
non-executable targets. See issue #7868.
|
| |
|
| |
|
|
|
|
| |
testing framework within CTest
|
|
|
|
| |
errors of Tutorial Step5 on Win98 using Visual Studio 6 when the path length of its build tree exceeds 72 characters. Crazy, perhaps. But this fixes the last real dashboard failure of the ExternalProject test.
|
| |
|
| |
|
|
|
|
| |
building, installing and testing on WATCOM dashboards. WATCOM STL support is still under development.
|
| |
|
| |
|
|
|
|
| |
*.dsp files cannot have hyphens in them. Add utility function GetVS6TargetName to replace hyphens with underscores when generating *.dsp file names. Use the function everywhere necessary in the VS6 generators. And, a workaround: VS6 uses ".\Debug" (for example) as an "$(IntDir)" value - strip any leading ".\" when processing a --config argument in the cmake --build handling code.
|
|
|
|
| |
installing. If none specified default to the cmake used to configure the outer/aggregating project.
|
|
|
|
|
|
|
|
|
|
| |
This teaches find_package to search
<prefix>/(share|lib)/cmake/<name>*/
for package configuration files. Packages that do not already have
files in a <prefix>/lib/<name>* directory can use this location to avoid
cluttering the lib directory.
|
|
|
|
|
| |
Versioning has been introduced to find_package, so the comment about it
is out of date.
|
|
|
|
| |
allow being configured as C. Thanks to Monsieur Francois Bertel for the patch.
|
|
|
|
|
|
|
|
|
| |
When the find_package command loads a module it sets several
<pkg>_FIND_XXX variables to communicate information about the command
invocation to the module. This restores the original state of the
variables when the command returns. This behavior is useful when a
find-module recursively calls find_package with NO_MODULE so that the
inner call does not change the values in the find-module.
|
| |
|
|
|
|
| |
CMake, and running Squish tests from ctest
|
|
|
|
| |
configure time as well as having custom commands that create them. Necessary for the Borland Makefiles generator to generate short path names in the makefile build rules. Also, make sure all custom commands chain together properly through the use of the sentinel files.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
ExternalProject test on the QNX continuous dashboard to pick up the latest KWStyle changes.
|
|
|
|
| |
ExternalProject test on the QNX continuous dashboard to pick up the latest KWStyle changes.
|
|
|
|
| |
ExternalProject test on the QNX continuous dashboard to pick up the latest KWStyle changes.
|
|
|
|
| |
ExternalProject test on the QNX continuous dashboard to pick up the latest KWStyle changes.
|
|
|
|
| |
for an external project. Add capability of customizing the download step. Add tests of empty projects. Better comments and error checking in AddExternalProject.cmake. In tests, use KWStyle from CVSHEAD to see if QNX continuous can build the latest KWStyle. Make KWStyle test depend on all previous test external projects so it builds last to catch other issues before any KWStyle compile errors.
|
| |
|
|
|
|
| |
building the projects that depend on a cvs or svn download method.
|
|
|
|
| |
fixing, more tests and documentation certain to follow as it gets used by others...
|
| |
|
| |
|
| |
|
| |
|
| |
|