- 06 May, 2014 1 commit
-
-
Take our CURSES_USE_NCURSES code path when CURSES_NEED_NCURSES is enabled even if CURSES_CURSES_LIBRARY also happens to be found. Applied-by:
Rolf Eike Beer <eike@sf-mail.de>
-
- 30 Apr, 2014 2 commits
-
-
Brad King authored
-
Brad King authored
In commit v3.0.0-rc1~103^2~3 (ExternalProject: Reattempt download when verification fails, 2014-01-15) a reference to ${CMAKE_COMMAND} was added to generate a reference to the CMake command in a cmake script. Escape the '$' so that the literal variable reference appears in the script instead of writing the path to the current cmake. This is necessary when the path to CMake contains spaces or other characters special to CMake syntax.
-
- 25 Apr, 2014 3 commits
- 24 Apr, 2014 3 commits
- 22 Apr, 2014 2 commits
-
-
Brad King authored
-
Fix cmOSXBundleGenerator::CreateCFBundle to place Info.plist under the same root directory as the rest of the bundle. Without this, Info.plist was placed into CMAKE_BINARY_DIR, not CMAKE_CURRENT_BINARY_DIR because the target path was not generated correctly.
-
- 18 Apr, 2014 2 commits
-
-
Brad King authored
-
-
- 16 Apr, 2014 5 commits
-
-
Brad King authored
-
Brad King authored
-
Brad King authored
-
Brad King authored
If archive_error_string returns NULL, use a placeholder string instead of crashing.
-
Brad King authored
Extend CMAKE_PLATFORM_IMPLICIT_LINK_DIRECTORIES with these paths. We already have the equivalents under /usr. Systems that have these directories have their dynamic loaders configured already. Do not allow them to appear in the RPATH explicitly.
-
- 11 Apr, 2014 3 commits
-
-
Brad King authored
-
Brad King authored
A 64-bit MinGW windres is named "i686-w64-mingw32.shared-windres". The get_filename_component NAME_WE mode may strip the ".shared-windres" part and cause the result to no longer contain "windres". Instead, match the "windres" name in the full CMAKE_RC_COMPILER value first, and use the get_filename_component code path only for other resource compilers.
-
Brad King authored
This module is for the Windows Resource Compiler, not Fortran.
-
- 10 Apr, 2014 6 commits
-
-
Brad King authored
-
Brad King authored
The PGI compiler does not define __SIZEOF_POINTER__ so use the __x86_64__ or __i386__ CPU macros to select a pointer size instead.
-
Brad King authored
-
Brad King authored
-
Brad King authored
Use the CMAKE_MATCH_* variables to simplify matching logic. Match either 3 or 4 version components. Do not fail when there are only three components available.
-
Brad King authored
Also state explicitly that the module is deprecated.
-
- 03 Apr, 2014 2 commits
-
-
Brad King authored
-
QT4_CREATE_MOC_COMMAND is given a moc_flags argument that contains the COMPILE_DEFINITIONS and a potentially large list of include directories. Since it is a macro, the ${moc_flags} reference is replaced with this content and sent through cmMakefile::ExpandVariablesInString (EVIS). Since commit v3.0.0-rc1~138^2 (Qt4: Use generator expression in COMPILE_DEFINITIONS, 2014-01-13) the COMPILE_DEFINITIONS value contains a '$' so the EVIS fast-path is no longer used. Instead the full cmCommandArgumentParserHelper is now used on the large input, which is very slow (since it was originally created for hand-written code). Change QT4_CREATE_MOC_COMMAND to a function instead of a macro to avoid passing large content through EVIS. This makes it significantly faster.
-
- 02 Apr, 2014 5 commits
-
-
Brad King authored
-
Brad King authored
These policies are triggered by the use of a particular compiler rather than outdated CMake code in a project. Avoid warning in every project that enables a language by not displaying the policy warning by default. Add variable CMAKE_POLICY_WARNING_CMP<NNNN> to control the warning explicitly; otherwise enable the warning with --debug-output or --trace. This breaks with strict policy convention because it does not provide developers with any warning about the behavior change by default. Existing projects will continue to build without a warning or change in behavior. When a developer changes the minimum required version of CMake in a project to a sufficiently high value (3.0), the project will suddenly get the new compiler id and may break, but at least the breakage comes with a change to the project rather than the version of CMake used to build it. Breaking strict policy convention is worthwhile in this case because very few projects will be affected by the behavior change but every project would have to see the warning if it were enabled by default.
-
Brad King authored
Add inline reST markup as appropriate. Word CMP0047 docs more like those of CMP0025. State explicitly that the policies must be set before the project or enable_language command calls.
-
Brad King authored
-
Brad King authored
-
- 31 Mar, 2014 2 commits
-
-
-
Clang -Wconditional-uninitialized warns otherwise.
-
- 26 Mar, 2014 2 commits
-
-
Brad King authored
-
Stephen Kelly authored
Do -> To.
-
- 20 Mar, 2014 1 commit
-
-
Brad King authored
-
- 19 Mar, 2014 1 commit
-
-
Brad King authored
-