summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Remove trailing whitespaceAlex Neundorf2011-09-153-49/+49
| | | | Alex
* Merge topic 'effective-platform-name'David Cole2011-09-1313-1/+1350
|\ | | | | | | | | | | 64c9b31 Xcode: Add test to demonstrate iOS project in Xcode 59a2265 Xcode: Use EFFECTIVE_PLATFORM_NAME reference in ComputeOutputDir
| * Xcode: Add test to demonstrate iOS project in XcodeDavid Cole2011-09-1212-0/+1345
| | | | | | | | | | | | | | | | | | | | Presently, this test is only run manually because not all machines have an iOS SDK, complications associated with certificates and code signing, having a device attached, ... If you're setup to do iOS dev work, you can easily run this test manually on your Mac using the Xcode generator and run the result in the simulator or on your attached device.
| * Xcode: Use EFFECTIVE_PLATFORM_NAME reference in ComputeOutputDirDavid Cole2011-09-121-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Caveats apply: only valid when not overriding default value for output dir *and* there is a CMAKE_XCODE_EFFECTIVE_PLATFORMS value. For now, CMAKE_XCODE_EFFECTIVE_PLATFORMS must be defined in each project, or in the cache for a build. Code relying on value of LOCATION and similar properties may not work if it depends on file existence on disk since CMake will not evaluate $(EFFECTIVE_PLATFORM_NAME). This feature is only enabled for making it easier to build Xcode iOS projects where the developer wants to be able to switch easily between simulator and device builds.
* | Merge topic 'CPackDeb-remove-stray-paren'David Cole2011-09-131-1/+1
|\ \ | | | | | | | | | | | | 85fd794 remove stray brace in CPackDeb documentation
| * | remove stray brace in CPackDeb documentationRolf Eike Beer2011-09-121-1/+1
| | |
* | | Merge topic 'CPack-DocFix-bug12449'David Cole2011-09-132-2/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | b7457de CPack fix template too 59204e1 CPack fix #12449 doc mispelled
| * | | CPack fix template tooEric NOULARD2011-09-091-1/+1
| | | |
| * | | CPack fix #12449 doc mispelledEric NOULARD2011-09-081-1/+1
| | | | | | | | | | | | | | | | CPACK_INSTALL_DIRECTORIES-->CPACK_INSTALLED_DIRECTORIESœ
* | | | Merge topic 'add-kwstyle-test'David Cole2011-09-132-6/+35
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | 3a0d632 KWStyle Test: Activate by default if KWStyle is found 91704ef Tests: Add a KWStyle test, equivalent to the make StyleCheck target
| * | | | KWStyle Test: Activate by default if KWStyle is foundDavid Cole2011-09-071-6/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Re-arrange the logic to look for KWStyle in the typical install locations and under the Dashboards/Support directory for the typical CMake dashboard machine. If it's there, turn on CMAKE_USE_KWSTYLE by default, thereby activating the KWStyle related custom targets and the KWStyle test.
| * | | | Tests: Add a KWStyle test, equivalent to the make StyleCheck targetDavid Cole2011-08-041-0/+13
| | | | |
* | | | | KWSys Nightly Date StampKWSys Robot2011-09-131-1/+1
| |_|/ / |/| | |
* | | | KWSys Nightly Date StampKWSys Robot2011-09-121-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-09-111-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-09-101-1/+1
| | | |
* | | | KWSys Nightly Date StampKWSys Robot2011-09-091-1/+1
| |/ / |/| |
* | | KWSys Nightly Date StampKWSys Robot2011-09-081-1/+1
| | |
* | | Merge topic 'fix-12446-no-cmake-E-build'David Cole2011-09-072-2/+1
|\ \ \ | | | | | | | | | | | | | | | | 96d106a CMake: Remove documentation for -E build (#12446)
| * | | CMake: Remove documentation for -E build (#12446)Matt McCormick2011-09-062-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | The '-E build build_dir' command was created and documented, but then morphed into '--build build_dir' instead, ... and then the -E documentation was never removed. This commit fixes that oversight.
* | | | Merge topic 'fix-12377-xcode-honor-g0'David Cole2011-09-071-7/+28
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | cb22afc Xcode: Honor -g0 to disable debugging (#12377)
| * | | | Xcode: Honor -g0 to disable debugging (#12377)Johan Bjork2011-09-061-7/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit changes ExtractFlag to remove all occurences of a flag, and only save the last one. (i.e., the dominant one according to GCC rules)
* | | | | Merge topic 'fix-12284-cpack-symlinks'David Cole2011-09-072-1/+3
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7b8dcdd CPack: Do not recurse through directory symlinks (#12284) d78bdb2 CMake: Write symlinks to directories as files in archives (#12284)
| * | | | | CPack: Do not recurse through directory symlinks (#12284)Johan Björk2011-09-061-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ...when building CPack archive-based packages (.tar.gz and similar) Rather, put the symlinks-to-directories into the archive as files, and expect/trust that the things the symlinks point to are also in the archive.
| * | | | | CMake: Write symlinks to directories as files in archives (#12284)Johan Björk2011-09-061-1/+2
| | |/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not recurse through directory symlinks when adding files. Recursing through directory symlinks will generate broken archives, i.e., they will look something like this: foo -> bar/bar foo/Info <- Shouldn't be in archive. bar/bar bar/bar/Info
* | | | | Merge topic 'fix-ctesttestcrash-test'David Cole2011-09-071-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | 339a321 Tests: Look for "Illegal" or "SegFault" in the output
| * | | | | Tests: Look for "Illegal" or "SegFault" in the outputDavid Cole2011-09-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | One of the dashmacmini5 runs of this test results in an "Illegal exception" detected instead of a segfault. For the purposes of this test, we're going to say that either is a "crash."
* | | | | | Merge topic 'CPackRPM-includeDir'David Cole2011-09-071-1/+3
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | f9e5277 CPackRPM fix #12305, include directories in RPM package
| * | | | | | CPackRPM fix #12305, include directories in RPM packageEric NOULARD2011-09-051-1/+3
| | |_|/ / / | |/| | | |
* | | | | | Merge topic 'fix-12260-fix-valgrind-output-parsing'David Cole2011-09-071-12/+12
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | eb4af16 CTest: Fixed valgrind output parsing (#12260)
| * | | | | | CTest: Fixed valgrind output parsing (#12260)Johannes Stallkamp2011-09-051-12/+12
| |/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previous code was missing some matches in the output. This commit fixes the regular expressions used for output matching to detect numbers reported with commas in them, too.
* | | | | | Merge topic 'CPackRPM-fix12366'David Cole2011-09-071-1/+1
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | b0f6a97 CPack fix #12366 components RPM packages have the same package name
| * | | | | | CPack fix #12366 components RPM packages have the same package nameEric NOULARD2011-09-051-1/+1
| |/ / / / / | | | | | | | | | | | | | | | | | | fix based on the patch provided by winfriedd
* | | | | | Merge topic 'fix-12370-no-space-in-target-name'David Cole2011-09-071-1/+3
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | e05e0f1 Xcode: No spaces in makefile target names (#12370)
| * | | | | | Xcode: No spaces in makefile target names (#12370)Johan Björk2011-09-051-1/+3
| |/ / / / / | | | | | | | | | | | | | | | | | | Don't use spaces for target names in the makefiles.
* | | | | | Merge topic 'generate_export_header'David Cole2011-09-0711-1/+115
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dbd776d Don't put what some compilers consider junk at the end of the line. 93d8d19 Add some more unit tests.
| * | | | | | Don't put what some compilers consider junk at the end of the line.Stephen Kelly2011-09-041-1/+1
| | | | | | |
| * | | | | | Add some more unit tests.Stephen Kelly2011-09-0210-0/+114
| | | | | | |
* | | | | | | Merge topic 'suppress-qt-warning'David Cole2011-09-071-0/+1
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7970192 Suppress Qt warning for dashmacmini5 builds 28ce8b7 Suppress Qt warning for dashmacmini5 builds
| * | | | | | | Suppress Qt warning for dashmacmini5 buildsDavid Cole2011-09-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The clang and icc compilers see two lines of warning with essentially the same message. But the second line does not say qglobal.h, so remove that part of the warning exclusion regex. See parent commit for further comments regarding this warning exclusion.
| * | | | | | | Suppress Qt warning for dashmacmini5 buildsDavid Cole2011-09-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Qt 4.7 and earlier produce a "This version of Mac OS X is unsupported" warning on Lion, even though they work fine once built. We'll upgrade this machine to use Qt 4.8 when it's officially released. Until then, suppress this warning so that we don't miss other "more real" warnings on the dashboard.
* | | | | | | | Merge topic 'fix-errors-from-cppcheck-issue-12440'David Cole2011-09-075-1/+8
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d1751fb ccmake: Fix off-by-one memory access error 4868921 Fix file() command descriptor leak on error f47393c CTest: Fix memory leaks on error
| * | | | | | | | ccmake: Fix off-by-one memory access errorThomas Jarosch2011-09-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Credit goes to "cppcheck". Signed-off-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
| * | | | | | | | Fix file() command descriptor leak on errorThomas Jarosch2011-09-021-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Credit goes to "cppcheck". Signed-off-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
| * | | | | | | | CTest: Fix memory leaks on errorThomas Jarosch2011-09-023-0/+5
| | |/ / / / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Credit goes to "cppcheck". Signed-off-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
* | | | | | | | Merge topic 'vs-compiler-id'David Cole2011-09-073-12/+3
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 38aab37 Set CMAKE_<lang>_COMPILER_ID for VS generators
| * | | | | | | | Set CMAKE_<lang>_COMPILER_ID for VS generatorsBrad King2011-09-023-12/+3
| |/ / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the VS generators do not support Intel C/C++ .icproj files and the MS tools do not include a Fortran compiler. Therefore we can always set the C and CXX compiler IDs to "MSVC" and the Fortran ID to "Intel". This fixes a regression in support for the Intel Fortran compiler under the VS plugin introduced by commit cd43636c (Modernize Intel compiler info on Windows, 2010-12-16). The commit moved the compiler information into platform files that only load when the proper compiler id is set. It worked for the NMake Makefiles generator but not for the VS IDE generator because it did not set the compiler id.
* | | | | | | | Merge topic 'fortran-format'David Cole2011-09-0724-7/+194
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 90efed6 Xcode: Honor Fortran_FORMAT target and source file property 5c0c635 Fortran: Add support for free- and fixed-form flags 47a0c75 VS: Map Fortran free- and fixed-format flags to IDE options d6e2a06 VS: Map per-source Fortran flags to IDE options
| * | | | | | | | Xcode: Honor Fortran_FORMAT target and source file propertyBrad King2011-09-011-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Convert the target property to the IFORT_LANG_SRCFMT build setting. Convert the source property to the per-source COMPILER_FLAGS setting.
| * | | | | | | | Fortran: Add support for free- and fixed-form flagsBrad King2011-08-3123-5/+161
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Define a "Fortran_FORMAT" target and source file property. Initialize the target property from a "CMAKE_Fortran_FORMAT" variable. Interpret values "FIXED" and "FREE" to indicate the source file format. Append corresponding flags to the compiler command line.