https://github.com/Kitware/CMake

sort by:
Revision Author Date Message Commit Date
66df520 fix 22 April 2016, 01:12:27 UTC
51caee9 fix 22 April 2016, 00:55:53 UTC
ea191ec fix 22 April 2016, 00:52:49 UTC
ea544e7 fix 22 April 2016, 00:47:23 UTC
c0aeeb0 fix 22 April 2016, 00:46:01 UTC
f96b67e fix 22 April 2016, 00:44:31 UTC
9c2358a fix 22 April 2016, 00:42:54 UTC
4a5ab4e fix 22 April 2016, 00:35:30 UTC
89a6bc2 merge 22 April 2016, 00:30:23 UTC
6064069 CUDA_ARCH_NAME made a list 22 April 2016, 00:28:06 UTC
5e6cf08 CUDA_ARCH_NAME made a list 22 April 2016, 00:19:15 UTC
e957a82 Fixed default 19 April 2016, 22:08:26 UTC
bcd40e1 Addressing code review notes. Better names for architectures 19 April 2016, 22:06:21 UTC
fc5e646 Merge branch 'master' into cuda_arch 19 April 2016, 21:56:55 UTC
7d4c99a CMake Nightly Date Stamp 19 April 2016, 04:01:05 UTC
fa4ae9f Merge topic 'refactor-cmListFileBacktrace' 0f96ef00 Remove unused cmake::IssueMessage overload 563bf9dd cmState: Remove unused entry point fields from snapshot data 7c36d206 cmListFileBacktrace: Refactor storage to provide efficient value semantics 1f6bd8a9 cmState: Avoid accumulating snapshot storage for backtraces 18b6676b cmState: Add Snapshot method to get bottom of call stack 18 April 2016, 15:07:07 UTC
ef71350 Merge topic 'minor-cleanups' 2faa8b36 Add call stack to unused/uninitialized variable warnings da07c506 cmLocalGenerator: Simplify IssueMessage implementation cc7aed77 cmLocalGenerator: Use own IssueMessage method c50285de cmOutputConverter: Assert construction with a valid snapshot b6ed71b1 cmMakefile: Move cmMakefileCall to .cxx file a559f0f6 cmWhileCommand: Simplify context construction 7503deb2 cmIfCommand: Simplify execution context construction 18 April 2016, 15:07:04 UTC
0f96ef0 Remove unused cmake::IssueMessage overload All callers now pass a full backtrace so we do not need the alternative that takes a cmListFileContext directly. Drop this overload to remove the code duplication. 18 April 2016, 13:21:19 UTC
563bf9d cmState: Remove unused entry point fields from snapshot data This information is now kept in cmMakefile::Backtrace. 18 April 2016, 13:21:19 UTC
7c36d20 cmListFileBacktrace: Refactor storage to provide efficient value semantics Since commit v3.4.0-rc1~321^2~2 (Genex: Store a backtrace, not a pointer to one, 2015-07-08) we treat cmListFileBacktrace instances as lightweight values. This was true at the time only because the backtrace information was kept in the cmState snapshot hierarchy. However, that forced us to accumulate a lot of otherwise short-lived snapshots just to have the backtrace fields available for reference by cmListFileBacktrace instances. Recent refactoring made backtrace instances independent of the snapshot hierarchy to avoid accumulating short-lived snapshots. This came at the cost of making backtrace values heavy again, leading to lots of string coying and slower execution. Fix this by refactoring cmListFileBacktrace to provide value semantics with efficient shared storage underneath. Teach cmMakefile to maintain its call stack using an instance of cmListFileBacktrace. This approach allows the current backtrace to be efficiently saved whenever it is needed. Also teach cmListFileBacktrace the notion of a file-level scope. This is useful for messages about the whole file (e.g. during parsing) that are not specific to any line within it. Push the CMakeLists.txt scope for each directory and never pop it. This ensures that we always have some context information and simplifies cmMakefile::IssueMessage. Push/pop a file-level scope as each included file is processed. This supersedes cmParseFileScope and improves diagnostic message context information in a few places. Fix the corresponding test cases to expect the improved output. 18 April 2016, 13:21:19 UTC
0256ea5 Merge topic 'cmPolicies-missing-include' cc684857 cmPolicies.cxx: Add missing include <ctype.h> for isdigit (#16066) 18 April 2016, 12:57:37 UTC
de3c7bd Merge topic 'AddDocumentationForEclipseVariables' 7b3a1069 Help: Document Eclipse-generator related variables (#15827) 18 April 2016, 12:57:32 UTC
f5c8a46 Merge topic 'cmake-host-solaris' 5dc6cfd6 Solaris: Add a CMAKE_HOST_SOLARIS variable (#16061) 18 April 2016, 12:57:29 UTC
0f6a8f7 Merge topic 'cmake-gui-osx-install-mkdir' 32d569af cmake-gui: Teach --install make destination directory (#16064) 18 April 2016, 12:57:27 UTC
21fb50d Merge topic 'FindMPI-intel-compiler' 2a99fae1 FindMPI: Recognize `.lib` file names for specification of link libraries c4417b09 FindMPI: Recognize /LIBPATH for specification of linker paths. 18 April 2016, 12:57:25 UTC
942e9d5 Merge topic 'FindGit-update-github-location' 19e8752b FindGit: Add new 'GitHub for Windows' user directory 18 April 2016, 12:57:23 UTC
7b3a106 Help: Document Eclipse-generator related variables (#15827) 18 April 2016, 12:56:19 UTC
49c4d66 CMake Nightly Date Stamp 18 April 2016, 04:01:05 UTC
6f139d3 CMake Nightly Date Stamp 17 April 2016, 04:01:05 UTC
94179ec CMake Nightly Date Stamp 16 April 2016, 04:01:08 UTC
19e8752 FindGit: Add new 'GitHub for Windows' user directory GitHub for Windows now installs in $ENV{LOCALAPPDATA}/Github/PortableGit*/cmd instead of $ENV{LOCALAPPDATA}/Github/PortableGit*/bin Search the new location first but keep the old one in case people have older versions installed. 15 April 2016, 18:59:06 UTC
cc68485 cmPolicies.cxx: Add missing include <ctype.h> for isdigit (#16066) 15 April 2016, 17:46:15 UTC
2a99fae FindMPI: Recognize `.lib` file names for specification of link libraries The Intel MPI compiler wrappers link against static MPI libraries simply by listing the libraries (no `-l`). 15 April 2016, 17:42:05 UTC
c4417b0 FindMPI: Recognize /LIBPATH for specification of linker paths. The Intel MPI wrappers use this form of -L to specify library locations. 15 April 2016, 17:42:05 UTC
5dc6cfd Solaris: Add a CMAKE_HOST_SOLARIS variable (#16061) 15 April 2016, 17:25:45 UTC
32d569a cmake-gui: Teach --install make destination directory (#16064) Ensure the destination directory exists before creating symlinks in it. 15 April 2016, 17:23:41 UTC
52dddef Merge branch 'release' 15 April 2016, 16:51:56 UTC
1f6bd8a cmState: Avoid accumulating snapshot storage for backtraces Changes during post-3.3/pre-3.4 development refactored storage of most configure-time information, including variable bindings and function scopes. All scopes (even short-lived) were kept persistently for possible future debugging features, causing huge accumulated memory usage. This was mostly addressed by commit v3.4.1~4^2 (cmState: Avoid accumulating snapshot storage for short-lived scopes, 2015-11-24). Since then we still keep short-lived scopes when they are needed for a backtrace. This is because since commit v3.4.0-rc1~378^2 (cmListFileBacktrace: Implement in terms of cmState::Snapshot, 2015-05-29) backtraces have been lightweight objects that simply point into the snapshot tree. While the intention of this approach was to avoid duplicating the call stack file path strings, the cost turned out to be holding on to the entire call stack worth of scope snapshots, which is much worse. Furthermore, since commit v3.4.0-rc2~1^2 (cmIfCommand: Issue CMP0054 warning with appropriate context, 2015-10-20) all conditions used in `if()` commands hold a backtrace for use in diagnostic messages. Even though the backtrace is short-lived it still causes the scope snapshot to be kept. This means that code like function(foo) if(0) endif() endfunction() foreach(i RANGE 1000000) foo() endforeach() accumulates storage for the function call scope snapshots. Fix this by partially reverting commit v3.4.0-rc1~378^2 and saving the entire call stack during cmListFileBacktrace construction. This way we can avoid keeping short-lived scope snapshot storage in all cases. 15 April 2016, 14:31:39 UTC
18b6676 cmState: Add Snapshot method to get bottom of call stack The bottom of the call stack is always a long-lived snapshot and can be saved for later use with cmOutputConverter. 15 April 2016, 14:31:39 UTC
2faa8b3 Add call stack to unused/uninitialized variable warnings In commit v2.8.4~32^2~14 (Use cmake::IssueMessage for warnings, 2010-12-07) these warnings became formatted. It is more informative to give the full call stack with such warnings. Also it is easier to implement warnings with a full call stack because we do not have to construct a custom backtrace with only the top. 15 April 2016, 14:13:12 UTC
da07c50 cmLocalGenerator: Simplify IssueMessage implementation This method was added by commit v3.4.0-rc1~424^2~6 (cmLocalGenerator: Add IssueMessage method, 2015-06-13) in order to reduce callers' dependency on cmMakefile. Currently the implementation of cmLocalGenerator::IssueMessage is just a copy of the post-configure code path in cmMakefile::IssueMessage. De-duplicate the implementation by simply calling the cmMakefile copy for now. This will simplify upcoming refactoring of backtraces. The dependency on cmMakefile can be removed by future work once that is done. 15 April 2016, 14:13:08 UTC
80bcbe2 CMake 3.5.2 15 April 2016, 12:48:23 UTC
cc7aed7 cmLocalGenerator: Use own IssueMessage method 15 April 2016, 12:34:05 UTC
c50285d cmOutputConverter: Assert construction with a valid snapshot We unconditionally use information from the snapshot so it must be valid. 15 April 2016, 12:34:05 UTC
b6ed71b cmMakefile: Move cmMakefileCall to .cxx file 15 April 2016, 12:32:15 UTC
a559f0f cmWhileCommand: Simplify context construction 15 April 2016, 12:31:59 UTC
7503deb cmIfCommand: Simplify execution context construction 15 April 2016, 12:29:42 UTC
c42aa3e CMake Nightly Date Stamp 15 April 2016, 04:01:05 UTC
003d4e5 CMake Nightly Date Stamp 14 April 2016, 04:01:06 UTC
f5da19e Merge topic 'cmState-rename-include-snapshot' c54ed781 cmState: Rename CallStack snapshots to IncludeFile 13 April 2016, 13:58:21 UTC
eae4cee Merge topic 'try_compile-config-flags' bd581a37 try_compile: Honor CMAKE_<LANG>_FLAGS_<CONFIG> changes (#16054) 82ef90fc cmCoreTryCompile: Factor out config lookup for re-use 13 April 2016, 13:58:18 UTC
6f2cc12 Merge topic 'FindMPI-docs' 87549054 FindMPI: Improve documentation formatting 13 April 2016, 13:58:14 UTC
1dc78fe Merge topic 'clang-tidy' 5e62444c Add options to run clang-tidy with the compiler 13 April 2016, 13:58:08 UTC
5e62444 Add options to run clang-tidy with the compiler Create a <LANG>_CLANG_TIDY target property (initialized by a CMAKE_<LANG>_CLANG_TIDY variable) to specify a clang-tidy command line to be run along with the compiler. 13 April 2016, 13:56:10 UTC
d0b2ec3 CMake Nightly Date Stamp 13 April 2016, 04:01:05 UTC
c54ed78 cmState: Rename CallStack snapshots to IncludeFile 12 April 2016, 20:08:24 UTC
a2ce4e8 CMake Nightly Date Stamp 12 April 2016, 04:01:07 UTC
bd581a3 try_compile: Honor CMAKE_<LANG>_FLAGS_<CONFIG> changes (#16054) In the `try_compile` source file signature we propagate the caller's value of `CMAKE_<LANG>_FLAGS` into the test project. Extend this to propagate `CMAKE_<LANG>_FLAGS_<CONFIG>` too instead of always using the default value in the test project. This will be useful, for example, to allow the MSVC runtime library to be changed (e.g. `-MDd` => `-MTd`). 11 April 2016, 15:25:08 UTC
82ef90f cmCoreTryCompile: Factor out config lookup for re-use Store the lookup of CMAKE_TRY_COMPILE_CONFIGURATION in a local variable so we can re-use it. 11 April 2016, 14:39:04 UTC
8754905 FindMPI: Improve documentation formatting 11 April 2016, 13:43:22 UTC
9ac11bc Merge topic 'test-RunCMake.BuildDepends-filesystem-workaround' f5e79004 Tests: Work around filesystem timestamp bugs in RunCMake.BuildDepends 11 April 2016, 13:39:00 UTC
3a556f0 Merge topic 'preallocate-condition-keywords' aff4a5fa cmConditionEvaluator: Use pre-allocated keywords in more places 11 April 2016, 13:38:58 UTC
335b543 Merge topic 'GetPrerequisites-more-dumpbin-paths' a1c40291 GetPrerequisites: Look for VS tools using environment variables c79f88b0 GetPrerequisites: add path of VS 10,11,12,14 in order to find dumpbin.exe 11 April 2016, 13:38:55 UTC
7c3fe7e CMake Nightly Date Stamp 11 April 2016, 04:01:05 UTC
0547e4d CMake Nightly Date Stamp 10 April 2016, 04:01:04 UTC
e2e2461 CMake Nightly Date Stamp 09 April 2016, 04:01:15 UTC
f5e7900 Tests: Work around filesystem timestamp bugs in RunCMake.BuildDepends The Custom-Symbolic-and-Byproduct case fails strangely on some filesystems used by our nightly testing. Somehow on the first build the `use-byproduct` output ends up with a timestamp older than `gen-byproduct-stamp` even though the build log clearly shows them build in the correct order (and must according to build system dependencies). Work around this problem by adding an extra delay before building `use-byproduct`. Tested-by: Gerhard Grimm <gerhard.grimm@detec.com> 08 April 2016, 14:51:01 UTC
aff4a5f cmConditionEvaluator: Use pre-allocated keywords in more places Inspired-by: Harry Mallon <Harry@codexdigital.com> 08 April 2016, 14:45:43 UTC
2b58cf8 Merge branch 'release' 08 April 2016, 13:05:33 UTC
f6c5958 Merge topic 'ninja-restat-custom-command-byproducts' add7abc8 Ninja: Restat custom command byproducts even with a SYMBOLIC output (#16049) ff805113 Ninja: Fix detection of custom command symbolic outputs 08 April 2016, 13:03:59 UTC
1baf2cb Merge topic 'drop-DNDEBUG-space' e888af97 MSVC: Drop space in `/DNDEBUG` flag for consistency (#16052) 08 April 2016, 13:01:53 UTC
2369f19 Merge topic 'ninja-object-rsp' 7731e44f Ninja: Honor CMAKE_NINJA_FORCE_RESPONSE_FILE for compile rules f9644a2d cmGlobalNinjaGenerator: Clarify logic for forcing use of response files 24c9106b cmNinjaTargetGenerator: Factor out helper for forced response file check 08 April 2016, 13:01:50 UTC
a1c4029 GetPrerequisites: Look for VS tools using environment variables The `VS*COMNTOOLS` environment variables specify locations of VS tools and are set during the VS installation. Use them in addition to the hard-coded default install locations. 08 April 2016, 12:48:20 UTC
c79f88b GetPrerequisites: add path of VS 10,11,12,14 in order to find dumpbin.exe 08 April 2016, 12:48:03 UTC
2f76eff CMake Nightly Date Stamp 08 April 2016, 04:01:07 UTC
e888af9 MSVC: Drop space in `/DNDEBUG` flag for consistency (#16052) We define `NDEBUG` without a space after the `-D` option for most compilers. Remove the space for MSVC (and Intel Fortran) for consistency. The MS compiler technically does not document that the `-D` argument may be separated from its value, though every version to date supports it. 07 April 2016, 14:54:43 UTC
7731e44 Ninja: Honor CMAKE_NINJA_FORCE_RESPONSE_FILE for compile rules 07 April 2016, 13:45:29 UTC
f9644a2 cmGlobalNinjaGenerator: Clarify logic for forcing use of response files Update the WriteBuild method to use a negative command line length limit to specify that we should force use of response files. 07 April 2016, 13:45:29 UTC
24c9106 cmNinjaTargetGenerator: Factor out helper for forced response file check 07 April 2016, 13:45:26 UTC
82c405c Merge topic 'branch_coverage_working_dir' c5ff34cc CTestCoverageCollectGCOV: specify base dir for GLOB_RECURSE 07 April 2016, 12:57:45 UTC
7d5a0f5 Merge topic 'branch_coverage_glob' 8ea1b0df CTestCoverageCollectGCOV: Improve documentation 425d7646 CTestCoverageCollectGCOV: Honor CTEST_EXTRA_COVERAGE_GLOB 07 April 2016, 12:57:41 UTC
cdce3cc Merge topic 'UseJava-cmake-command' fa382ae8 UseJava: use CMAKE_COMMAND instead of direct cmake call 07 April 2016, 12:57:35 UTC
47e358d Merge topic 'ExternalProject-TLS_VERIFY-fixes' 4d8c988c ExternalProject: Fix file download script with CMAKE_TLS_{VERIFY,CAINFO} 23a71e4e ExternalProject: Tell Git not to verify certs only if TLS_VERIFY is OFF 07 April 2016, 12:57:29 UTC
8ea1b0d CTestCoverageCollectGCOV: Improve documentation Clean up prose and mention support for CTEST_EXTRA_COVERAGE_GLOB. 07 April 2016, 12:53:30 UTC
425d764 CTestCoverageCollectGCOV: Honor CTEST_EXTRA_COVERAGE_GLOB Teach CTestCoverageCollectGCOV to honor the CTEST_EXTRA_COVERAGE_GLOB variable. When this variable is set, this module will glob for matching source files that were not covered and include them in the resulting tar file. 07 April 2016, 12:53:30 UTC
8de04f6 CMake Nightly Date Stamp 07 April 2016, 04:01:05 UTC
4d8c988 ExternalProject: Fix file download script with CMAKE_TLS_{VERIFY,CAINFO} Avoid generating incorrect code such as set(CMAKE_TLS_VERIFY set(CMAKE_TLS_VERIFY 1)) when one of these variables is set in the calling project. 06 April 2016, 20:49:13 UTC
23a71e4 ExternalProject: Tell Git not to verify certs only if TLS_VERIFY is OFF Since commit 272779ce (ExternalProject: Allow TLS_VERIFY for git clones, 2016-04-01) we pass the `-c http.sslVerify=false` option to `git clone` even if no explicit `TLS_VERIFY` option was set. This changes behavior because we used to use the default Git behavior by default. Revise the logic to preserve the old default behavior by passing the new option only if `TLS_VERIFY` was explicitly passed as `OFF`. While at it, also honor `CMAKE_TLS_VERIFY` if the explicit `TLS_VERIFY` option is not given. 06 April 2016, 20:49:13 UTC
fa382ae UseJava: use CMAKE_COMMAND instead of direct cmake call Author: dancing-leaves <dancing-leaves@users.noreply.github.com> 06 April 2016, 17:46:51 UTC
ae2fa89 Merge topic 'fortran-line-directives-no-dirs' f831d752 cmFortranParser: Skip #line directives that do not name files 06 April 2016, 13:30:03 UTC
7b3a561 Merge topic 'FindOpenSSL-names-per-dir' b1484403 FindOpenSSL: Prefer libs early in search path regardless of name (#15887) 06 April 2016, 13:30:00 UTC
ffe2dbb Merge topic 'mingw-w64-Fortran-platform' 8c4f100a Fortran: Fix platform id detection on mingw-w64 66fa6143 CMakeDetermineFortranCompiler: Modernize conventions 06 April 2016, 13:29:58 UTC
0a628f0 Merge topic 'FindGSL-doc-typo' 2308764b FindGSL: Fix typo in documentation 06 April 2016, 13:29:56 UTC
87dddf0 Merge topic 'find-blas-lapack-Fortran-only' 1694112d Find{BLAS,LAPACK}: Fix when used in pure Fortran projects (#16039) 06 April 2016, 13:29:53 UTC
8898a92 CMake Nightly Date Stamp 06 April 2016, 04:01:08 UTC
9729dfb Merge branch 'ninja-restat-custom-command-byproducts' into release 05 April 2016, 20:27:08 UTC
add7abc Ninja: Restat custom command byproducts even with a SYMBOLIC output (#16049) The change in commit v3.5.0-rc1~198^2 (Ninja: Always re-run custom commands that have symbolic dependencies, 2015-11-19) broke the byproducts feature added by commit v3.2.0-rc1~340^2~2 (Add an option for explicit BYPRODUCTS of custom commands, 2014-11-13) when SYMBOLIC outputs also appear. This case occurs with AUTORCC-generated custom targets because the output is SYMBOLIC (to always run) and the generated file is a byproduct (for restat so dependents do not run unnecessarily). The two use cases conflict because Ninja does not support per-output restat. Favor restat whenever byproducts are present because it is required for byproducts to work correctly. In use cases where we want an always-run chain we simply will not be able to also use byproducts. 05 April 2016, 20:20:28 UTC
ff80511 Ninja: Fix detection of custom command symbolic outputs Fix logic introduced by commit v3.5.0-rc1~198^2 (Ninja: Always re-run custom commands that have symbolic dependencies, 2015-11-19) to not consider only the last output. We need to know if any output is SYMBOLIC, so stop checking as soon as one is found. 05 April 2016, 20:19:52 UTC
4ffd85c Merge branch 'fortran-line-directives-no-dirs' into release 05 April 2016, 16:59:57 UTC
f831d75 cmFortranParser: Skip #line directives that do not name files Since commit v3.5.0-rc1~241^2~1 (cmFortranParser: Parse #line directives, 2015-11-02) our Fortran dependency scanner parses `#line` directives to extract the named files. However, some compilers produce `#line` directives that name directories instead of files. Work around such cases by verifying that the extracted path names a file and not a directory. 05 April 2016, 16:59:45 UTC
back to top