summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Clarify CMAKE_MODULE_PATH documentationBrad King2010-02-181-4/+4
| | | | | Reword the documentation to make it clear that the variable can be a list of directories.
* KWSys Nightly Date StampKWSys Robot2010-02-181-1/+1
|
* Add support for QtDeclartive module.Clinton Stimpson2010-02-182-3/+12
|
* Fix problem with ExternalProject test in in-source builds.David Cole2010-02-171-0/+11
|
* A few small changed from Pat Marion (in VTK CVS too)Marcus Hanwell2010-02-171-2/+2
|
* Applied patch from Pat Marion - modules header macro.Marcus Hanwell2010-02-171-6/+12
| | | | | | This modifies the behavior of PYTHON_WRITE_MODULES_HEADER, should be backwards compatible. Also marked a couple of the variables generated by adding Python modules as advanced.
* Do not force frameworks on Mac OS X - never worked well.Marcus Hanwell2010-02-171-16/+0
|
* KWSys Nightly Date StampKWSys Robot2010-02-171-1/+1
|
* FortranCInterface: Fix PathScale detection againBrad King2010-02-161-0/+6
| | | | | | | | | | | PathScale Fortran mangles module symbols as "MY_SUB.in.MY_MODULE" and also requires "my_module_" when the module is imported. We cannot provide the symbol with ".in." mangling so we should not provide "my_module_" because it would duplicate the one in the Fortran-provided object file. Commit "FortranCInterface: Fix PathScale detection" (2010-01-22) already made the same fix for the non-underscore module case.
* KWSys Nightly Date StampKWSys Robot2010-02-161-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-02-151-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-02-141-1/+1
|
* -fix bug for Eclipse projects where targets which are in a subdir which has ↵Alexander Neundorf2010-02-131-19/+19
| | | | | | | | | | | | | | the same name as the project (... and so the linked resource) could not be built http://public.kitware.com/Bug/view.php?id=9978 Now instead of one linked resource for each project() just one linked resource to the top level source directory is created. This should really avoid this type of name clashes. And to me it looks also much less confusing. Hopefully the name "[Source directory]" containing a space and square brackets doesn't lead to problems somewhere. Here it works. Alex
* KWSys Nightly Date StampKWSys Robot2010-02-131-1/+1
|
* Preemptively fix line too long problem before tomorrow's dashboard has a ↵David Cole2010-02-121-3/+4
| | | | chance to complain about it.
* Make a common function that prints the status during the checks for working ↵David Cole2010-02-124-9/+36
| | | | compilers. Call it from all of the CMakeTesten_US.UTF-8Compiler.cmake files. In the message, print the full path to the tested compiler only for the Makefile generators. For Xcode and Visual Studio generators, print the generator instead so that users are not misled with the full path to a compiler that the generator may not even use. Xcode and Visual Studio have their own mechanisms for choosing the compiler to use during try_compile and build...
* Fix for issue #9125 - invent CMAKE_XCODE_ATTRIBUTE_* variable mechanism. If ↵David Cole2010-02-121-0/+15
| | | | there are variables that begin with CMAKE_XCODE_ATTRIBUTE_ then add corresponding attributes into the generated Xcode project file.
* Fix KWSYS_PLATFORM_INFO_TEST when user removes treeBrad King2010-02-121-1/+1
| | | | | | | | | | In commit 'Create KWSYS_PLATFORM_INFO_TEST macro' (2009-11-20) we implemented the macro to use a cache entry to avoid re-running the try_compile(). However, the output copied from the try_compile is needed on every configure. If the user wipes out the build tree but not the cache file then the try_compile() will not re-run to recreate the needed file. We address the problem by teaching the macro to run the try_compile() whenever its output file does not exist.
* Fix rule hash persistence file generationBrad King2010-02-122-4/+16
| | | | | | | | | | | | | | | | | | | | | We store custom command rule hashes in CMakeFiles/CMakeRuleHashes.txt persistently across CMake runs. When the rule hash changes we delete the custom command output file and write a new hash into the persistence file. This functionality was first added by the commit 'Introduce "rule hashes" to help rebuild files when rules change.' (2008-06-02). However, the implementation in cmGlobalGenerator::CheckRuleHashes kept the file open for read when attempting to rewrite a new file. On Windows filesystems this prevented the new version of the file from being written! This caused the first set of rule hashes to be used forever within a build tree, meaning that all custom commands whose rules changed would be rebuilt every time CMake regenerated the build tree. In this commit we address the problem by splitting the read and write operations into separate methods. This ensures that the input stream is closed before the output stream opens the file.
* KWSys Nightly Date StampKWSys Robot2010-02-121-1/+1
|
* Add a high COST value to BootstrapTest so that it will be scheduled first in ↵Zach Mullen2010-02-111-0/+2
| | | | parallel ctest executions.
* KWSys Nightly Date StampKWSys Robot2010-02-111-1/+1
|
* Fix for fix for issue #2336 - do not specify CMAKE_BUILD_TYPE when the ctest ↵David Cole2010-02-101-1/+2
| | | | -C configuration type string is empty.
* Make CTest.UpdateCVS robust to some cvs clientsBrad King2010-02-102-2/+3
| | | | | | | | | | | | | | Commit "Teach CTest.Update tests to strongly check entries" (2010-02-09) started checking Update.xml entries strongly. This revealed that some cvs clients report "U CTestConfig.cmake" during update even though the file did not change and it selects the same revision. As a result the test fails with Update.xml has extra unexpected entries: Updated{CTestConfig.cmake} We fix the test to tolerate this particular extra entry without failing.
* Fix configure time error that occurs when there is a backslash in the HOME ↵David Cole2010-02-101-1/+2
| | | | environment variable.
* Do not warn for unknown CTest UPDATE_TYPEBrad King2010-02-101-7/+0
| | | | | | | | | | | | | In the CTest module we previously warned if the source directory did not contain known version control directories. The message was: "CTest cannot determine repository type. Please set UPDATE_TYPE to 'cvs' or 'svn'. CTest update will not work." This was confusing when building sources from a tarball. Furthermore, we now support many more version control tools. This feature is now mature enough that the warning causes confusion more than it provides real help. We simply remove it.
* Detect Git repositories for CTest UPDATE_TYPEBrad King2010-02-101-0/+7
| | | | | The CTest module configures the command-line CTest dashboard mode. We teach it to recognize .git directories.
* Simplify CTest.cmake module with ELSEIFBrad King2010-02-101-29/+17
| | | | | We use ELSEIF to simplify the cascading IF blocks for detecting version control tools.
* KWSys Nightly Date StampKWSys Robot2010-02-101-1/+1
|
* Fix for bug #10257, NSIS could remove a PATH if it was too longBill Hoffman2010-02-091-0/+9
|
* Teach CTest.UpdateGIT test to fake file timestampBrad King2010-02-092-0/+12
| | | | | | | We wrap the git executable in a shell script that touches one source file after 'git pull'. This makes the file newer than the index even though it has not actually changed. If CTest does not refresh the index properly then the test will fail with a bogus modified file.
* cmCTestGIT: Refresh index for local modificationsBrad King2010-02-091-2/+8
| | | | | | | | We use 'git diff-index' to detect local modifications after pull. On some filesystems the work tree timestamps of a few files may be dated after the index, making them appear as locally modified. We address the problem by using 'git update-index --refresh' to refresh the index and avoid false local modifications.
* Teach CTest.Update tests to strongly check entriesBrad King2010-02-091-19/+47
| | | | | | Previously these tests just checked for matching file names in the Update.xml files. Now we check the update types (Updated, Modified, or Conflicting) and reject unexpected extra entries.
* cmCTestBZR: Strip trailing slashes from pathsBrad King2010-02-091-2/+6
| | | | | | | Our internal path processing methods assume no trailing slashes, but bzr adds trailing slashes to updated directories. This can lead to empty entries in Update.xml files. We address the problem by stripping the slashes as soon as they are parsed.
* current release stuffBill Hoffman2010-02-093-1/+42
|
* KWSys Nightly Date StampKWSys Robot2010-02-091-1/+1
|
* Moved call to cache CDash version information to cmCTest::initialize. Also ↵Zach Mullen2010-02-083-5/+9
| | | | added a 3 second timeout when requesting the version from the server. Added an option to the CTestConfiguration that will be used to determine whether to query the version information at all. (Behavior for this setting is not yet defined.) Updated CMake's local CDash version setting to 1.6.
* KWSys Nightly Date StampKWSys Robot2010-02-081-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-02-071-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-02-061-1/+1
|
* KWSys Nightly Date StampKWSys Robot2010-02-051-1/+1
|
* Fix HPUX issue with test, by doing the query to cdash for its version before ↵Bill Hoffman2010-02-051-1/+3
| | | | any test is started.
* Support for relative paths to executables in MemCheck tests. Also fixed a ↵Zach Mullen2010-02-041-1/+3
| | | | bug causing memcheck args to be overwritten repetitively.
* KWSys Nightly Date StampKWSys Robot2010-02-041-1/+1
|
* Re-enabled Scheduler test and fixed the underlying problem.Zach Mullen2010-02-032-11/+11
|
* Disable Scheduler test until underlying problem is resolved.Zach Mullen2010-02-031-10/+10
|
* Add unit test to ensure that CTestCostData scheduling works correctlyZach Mullen2010-02-035-0/+79
|
* KWSys Nightly Date StampKWSys Robot2010-02-031-1/+1
|
* Recognize the Compaq Fortran compilerBrad King2010-02-021-0/+5
| | | | | | | | | | The compiler documents symbols _DF_VERSION_ and _VF_VERSION_ but they do not seem to be available to the preprocessor. Instead we add a vendor query table entry for Compaq. Running "f90 -what" produces Compaq Visual Fortran Optimizing Compiler Version ... This clearly identifies the compiler.
* KWSys Nightly Date StampKWSys Robot2010-02-021-1/+1
|
generated by cgit v0.12 at 2025-02-12 00:22:52 (GMT)