| 80bcbe2 | Brad King | 15 April 2016, 12:48:23 UTC | CMake 3.5.2 | 15 April 2016, 12:48:23 UTC |
| 9729dfb | Brad King | 05 April 2016, 20:27:08 UTC | Merge branch 'ninja-restat-custom-command-byproducts' into release | 05 April 2016, 20:27:08 UTC |
| add7abc | Brad King | 05 April 2016, 20:20:28 UTC | 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 | Brad King | 05 April 2016, 19:31:47 UTC | 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 | Brad King | 05 April 2016, 16:59:57 UTC | Merge branch 'fortran-line-directives-no-dirs' into release | 05 April 2016, 16:59:57 UTC |
| f831d75 | Brad King | 05 April 2016, 16:57:15 UTC | 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 |
| dff812c | Brad King | 05 April 2016, 13:52:55 UTC | Merge branch 'FindGSL-doc-typo' into release | 05 April 2016, 13:52:55 UTC |
| 2308764 | Pierrick Koch | 04 April 2016, 14:35:50 UTC | FindGSL: Fix typo in documentation s/GSL_CLBAS_LIBRARY/GSL_CBLAS_LIBRARY/ | 05 April 2016, 13:52:43 UTC |
| 58a5710 | Brad King | 01 April 2016, 19:47:03 UTC | Merge branch 'fix-target-alias-in-subdir' into release | 01 April 2016, 19:47:03 UTC |
| 0e44f48 | Brad King | 01 April 2016, 14:26:08 UTC | Rename local target lookup methods to clarify purpose Rename methods: * `cmMakefile::Find{ => LocalNonAlias}Target` * `cmLocalGenerator::Find{ => LocalNonAlias}GeneratorTarget` These names clarify that they are for directory-local target names and do not consider alias targets. | 01 April 2016, 19:44:16 UTC |
| bc30f8b | Brad King | 01 April 2016, 13:13:16 UTC | Fix lookup of an ALIAS target outside aliased target's directory (#16044) Refactoring in commit v3.5.0-rc1~272^2~11 (cmTarget: Implement ALIAS in terms of name mapping, 2015-10-25) accidentally introduced logic that assumes ALIAS targets always reference targets in their own directory. Fix this and add a test case. The configure-step fix is that `cmMakefile::FindTarget` should not consider aliases. The purpose of this method is just to look up targets local to a directory. Since ALIAS and normal targets share a namespace we know a locally defined target will never collide with an ALIAS target anyway. The method has 3 call sites, and this change is safe for all of them: * `cmInstallCommand::HandleTargetsMode`: Rejects aliases before the call. * `cmFLTKWrapUICommand::FinalPass`: Should never have considered aliases. * `cmMakefile::FindTargetToUse`: Falls back to a global lookup anyway. The generate-step fix is that `cmLocalGenerator::FindGeneratorTarget` should not consider aliases. This method is the generate-step equivalent to the above. The method has 2 call sites, and this change is safe for both of them: * `cmInstallTargetGenerator::Compute`: Never uses an alias target name. * `cmLocalGenerator::FindGeneratorTargetToUse`: Falls back to global lookup. Reported-by: Matteo Settenvini <matteo@member.fsf.org> | 01 April 2016, 19:44:16 UTC |
| 8f8a0bf | Brad King | 31 March 2016, 17:23:16 UTC | Merge branch 'backport-asm-includes' into release | 31 March 2016, 17:23:16 UTC |
| 677c091 | Gregor Jasny | 25 March 2016, 22:18:07 UTC | ASM: Add missing <INCLUDES> placeholder for "compile" rules This placeholder was added to the compilation rules for other languages by commit v3.4.0-rc1~342^2 (Factor an <INCLUDES> placeholder out of <FLAGS> in rule variables, 2015-07-13) but ASM was incorrectly left out. Signed-off-by: Gregor Jasny <gjasny@googlemail.com> | 31 March 2016, 17:22:46 UTC |
| 8fdb2c5 | Brad King | 28 March 2016, 13:24:18 UTC | Merge branch 'xcode73-xctest-location' into release | 28 March 2016, 13:24:18 UTC |
| a364d25 | Gregor Jasny | 25 March 2016, 21:20:14 UTC | Xcode: Fixup XCTest bundle location for Xcode 7.3 Prior to Xcode 7.3 a XCTest bundle was built like an ordinary bundle. But starting with Xcode 7.3 it is implicitely built as a plugin for the test host. It looks like in that case the 'Build Products Path' is ignored. This patch simply sets the CMake target output path to the value Xcode expects internally to get a matching view of both. The command: xcodebuild -showBuildSettings -target CocoaExampleTests -configuration Debug Output with Xcode 7.2: TARGET_BUILD_DIR = .../Tests/XCTest/Debug Output with Xcode 7.3 TARGET_BUILD_DIR = .../Tests/XCTest/Debug/CocoaExample.app/Contents/PlugIns Signed-off-by: Gregor Jasny <gjasny@googlemail.com> | 28 March 2016, 13:23:35 UTC |
| 64130a7 | Brad King | 24 March 2016, 13:56:42 UTC | CMake 3.5.1 | 24 March 2016, 13:56:42 UTC |
| 277b756 | Brad King | 23 March 2016, 20:18:08 UTC | Merge branch 'fix-variable_watch-reallocation' into release | 23 March 2016, 20:18:08 UTC |
| c610402 | Yves Frederix | 23 March 2016, 09:37:51 UTC | Avoid occasional use-after-free when a variable watch is executed Re-lookup a variable value when an associated VariableWatch is executed in cmMakefile::GetDefinition. This fixes a problem with 'def' sometimes becoming invalid due to memory reallocation inside an std::vector. In this case, the problem was that if the call to VariableAccessed actually executed a callback function, the internal state of the makefile has changed due to the associated function scope being pushed. This in turn implies that a new cmDefinitions instance was pushed in cmMakefile::VarTree. As cmLinkedTree is based on an std::vector, this push can have triggered reallocation of its internal memory buffer. However, as the value of 'def', which was computed on method entry, actually points to a property of one of the cmDefinitions instances in cmMakefile::VarTree, reallocation can invalidate the value of 'def' so that it cannot simply be returned at the end of the function. The solution implemented here is to simply lookup the value of 'def' again. | 23 March 2016, 20:17:36 UTC |
| f77ad2c | Brad King | 22 March 2016, 15:36:45 UTC | Merge branch 'FindCUDA-verbatim' into release | 22 March 2016, 15:36:45 UTC |
| 72a97b7 | Brad King | 22 March 2016, 15:04:14 UTC | FindCUDA: Fix regression in separate compilation (#16027) Since commit v3.5.0-rc1~47^2 (FindCUDA: Support special characters in path, 2016-01-15) our add_custom_command calls use VERBATIM so that CMake will automatically quote special characters correctly. Fix the separate compilation code path to not add its own quoting when the VERBATIM option will be used. | 22 March 2016, 15:05:02 UTC |
| 2c3b8a1 | Brad King | 21 March 2016, 13:08:25 UTC | Merge branch 'fix-repeat-pkg-config' into release | 21 March 2016, 13:08:25 UTC |
| 6f4f905 | Ben Boeckel | 18 March 2016, 19:48:56 UTC | FindPkgConfig: set correctly named variables in cache (#15903) The fix in commit v3.5.0-rc1~27^2 (FindPkgConfig: set standard variables in the cache, 2016-01-20) added the wrong variable name to the cache. The test was only testing that the cache variable existed, not that it also had the correct value. Update the test to ensure that the cache value matches the local variable value. Reported-by: Bernd Lörwald | 21 March 2016, 12:58:12 UTC |
| d9857c8 | Brad King | 18 March 2016, 15:15:15 UTC | Merge branch 'cpack-osx-optional-CoreServices' into release | 18 March 2016, 15:15:15 UTC |
| d84ba66 | Brad King | 18 March 2016, 12:49:02 UTC | CPack: Avoid using OS X CoreServices if compiler fails on header (#16021) Some compilers on OS X report errors in the CoreServices framework headers. Check for support of the header ahead of time and compile the relevant code only when the header is available. | 18 March 2016, 15:12:51 UTC |
| 1b03412 | Brad King | 17 March 2016, 20:30:00 UTC | Merge branch 'cmake-gui-osx-identifier' into release | 17 March 2016, 20:30:00 UTC |
| 7b990e8 | Brad King | 17 March 2016, 20:06:54 UTC | cmake-gui: Populate CFBundleIdentifier in our Info.plist file (#16023) | 17 March 2016, 20:07:39 UTC |
| 15a5653 | Brad King | 17 March 2016, 18:49:35 UTC | Merge branch 'cpack-osx-no-carbon' into release | 17 March 2016, 18:49:35 UTC |
| c718070 | Sean McBride | 17 March 2016, 14:47:44 UTC | CPack: Avoid requiring Carbon framework on OS X (#16021) In commit v3.5.0-rc1~232^2 (CPackDMG: Add support for multilingual SLAs, 2015-10-19) we added use of the Carbon framework in order to get access to its APIs to convert Script Manager RegionCode values. This is not necessary. Instead we can use CoreServices. While at it, replace individual CoreFoundation includes with including the entire framework, which is the correct way. | 17 March 2016, 17:53:51 UTC |
| 4ea249a | Brad King | 15 March 2016, 14:11:27 UTC | Merge branch 'ios-install-combined-one-arch' into release | 15 March 2016, 14:11:27 UTC |
| e3fc289 | Ruslan Baratov | 14 March 2016, 10:27:53 UTC | Fix iOS combined feature for single architecture targets If list of valid target architectures is empty for given SDK then there will be no VALID_ARCHS build setting returned by Xcode. Return "" (empty string) explicitly in this case. This may happens if CMAKE_IOS_INSTALL_COMBINED is ON but only one architecture used in target. | 15 March 2016, 14:09:50 UTC |
| 44bbd2a | Brad King | 15 March 2016, 14:00:26 UTC | Merge branch 'FindBoost-optional-indirect-depends' into release | 15 March 2016, 14:00:26 UTC |
| e2f387f | Roger Leigh | 14 March 2016, 13:49:39 UTC | FindBoost: Tolerate missing indirect dependencies (#16013) Depending upon the configuration, certain components may or may not be installed, for example Boost.Regex, but other components may still have header dependencies upon these components which will obviously fail to work. Since we can't make a sensible determination with the hardcoded dependency information, we choose to interpret these dependencies less strictly. | 15 March 2016, 13:54:58 UTC |
| b369959 | Brad King | 08 March 2016, 13:44:49 UTC | CMake 3.5.0 | 08 March 2016, 13:44:49 UTC |
| 0e02c69 | Brad King | 07 March 2016, 16:03:50 UTC | Merge branch 'doc-find-python-call-order' into release | 07 March 2016, 16:03:50 UTC |
| 743f2a8 | Brad King | 07 March 2016, 15:56:31 UTC | FindPython{Interp,Libs}: Clarify recommended call order Improve wording in our advice about how to call both of these modules. | 07 March 2016, 15:56:31 UTC |
| 15a4afe | Brad King | 07 March 2016, 15:09:33 UTC | Merge branch 'vs14-debug-enum-older-toolsets' into release | 07 March 2016, 15:09:33 UTC |
| 3aa6fea | Brad King | 24 February 2016, 17:15:48 UTC | VS: Fix VS 2015 .vcxproj debug setting for older toolsets (#15986) Since commit v3.4.2~2^2 (VS: Fix VS 2015 .vcxproj file value for GenerateDebugInformation, 2016-01-08) we generate invalid project files for the v110 and v120 toolsets. VS complains: C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(639,9): error MSB4030: "Debug" is an invalid value for the "GenerateDebugInformation" parameter of the "Link" task. The "GenerateDebugInformation" parameter is of type "System.Boolean". This reveals that our VS flag map selection should be based on the toolset instead of the version of VS. However, that will be a non-trivial change so for now fix this particular use case by hard-coding a correction to the flag map. Reported-by: Gregor Jasny <gjasny@googlemail.com> | 07 March 2016, 15:09:09 UTC |
| 6e6f4d8 | Brad King | 24 February 2016, 15:13:45 UTC | Merge branch 'doc-typos' into release | 24 February 2016, 15:13:45 UTC |
| 33507e2 | Ashley Whetter | 21 February 2016, 15:17:07 UTC | Help: Fix typos in cmake-packages.7 manual | 24 February 2016, 15:05:24 UTC |
| c8d5db9 | Brad King | 19 February 2016, 18:06:38 UTC | Merge branch 'doc-cmake-E-details' into release | 19 February 2016, 18:06:38 UTC |
| b347503 | Bartosz Kosiorek | 19 February 2016, 16:48:20 UTC | Help: Clarify `cmake -E` command behavior with respect to file existence | 19 February 2016, 18:03:09 UTC |
| d203761 | Brad King | 18 February 2016, 15:41:26 UTC | CMake 3.5.0-rc3 | 18 February 2016, 15:41:26 UTC |
| 3dd420b | Brad King | 17 February 2016, 20:25:44 UTC | Merge branch 'FindCUDA-verbatim' into release | 17 February 2016, 20:25:44 UTC |
| 1911cda | Brad King | 17 February 2016, 20:14:22 UTC | FindCUDA: Fix regression under Visual Studio generators Since commit v3.5.0-rc1~47^2 (FindCUDA: Support special characters in path, 2016-01-15) our add_custom_command calls use VERBATIM so that CMake will automatically quote special characters correctly. However, this breaks the special `$(VCInstallDir)` placeholder used with Visual Studio generators. Since we do not support preservation of such placeholders with VERBATIM (see issue #15001) we must fall back to not using VERBATIM when the placeholder is used. A better fix would be to stop using `$(VCInstallDir)` and use the value of `CMAKE_${CUDA_C_OR_CXX}_COMPILER` instead, but that will require additional semantic and documentation changes. For now simply fix the regression with the above approach. Reported-by: Stephen Sorley <Stephen.Sorley@jhuapl.edu> | 17 February 2016, 20:20:56 UTC |
| ef10f52 | Brad King | 17 February 2016, 19:03:05 UTC | Merge branch 'fix-static-private-non-target-depends' into release | 17 February 2016, 19:03:11 UTC |
| 87f44b7 | Brad King | 17 February 2016, 18:34:15 UTC | Fix export of STATIC library PRIVATE non-target dependencies In commit v3.5.0-rc1~43^2 (Fix export of STATIC library PRIVATE dependencies with CMP0022 NEW, 2016-01-15) we taught target_link_libraries to generate `$<LINK_ONLY:$<TARGET_NAME:dep>>` in INTERFACE_LINK_LIBRARIES instead of `$<LINK_ONLY:dep>` so that `dep` can be recognized as a target name and updated during export. However, this approach does not work when `dep` is just a plain library name and not a target because `$<TARGET_NAME:...>` requires the name of a reachable target. Since we do not know during target_link_libraries whether the name will correspond to a reachable target or not, we cannot inject the `$<TARGET_NAME:...>` expression. Revert this change and solve the original problem instead by teaching the export logic to recognize and update target names directly in `$<LINK_ONLY:...>` expressions. Reported-by: Ben Boeckel <ben.boeckel@kitware.com> | 17 February 2016, 19:01:11 UTC |
| a13a6ee | Brad King | 17 February 2016, 15:16:14 UTC | Merge branch 'backport-doc-install-component-association' into release | 17 February 2016, 15:16:14 UTC |
| 70f2708 | Brad King | 17 February 2016, 15:11:01 UTC | Help: Clarify install(TARGETS) INCLUDES DESTINATION option The option does not actually participate in argument groups like the others because it does not actually install anything. Fix the order in the documentation accordingly. Reported-by: Daniel Wirtz <daniel.wirtz@simtech.uni-stuttgart.de> | 17 February 2016, 15:12:10 UTC |
| 9dff5d9 | Brad King | 17 February 2016, 14:22:47 UTC | Merge branch 'de-deprecate-CMakeForceCompiler' into release | 17 February 2016, 14:22:47 UTC |
| beaa4fa | Brad King | 17 February 2016, 14:14:20 UTC | CMakeForceCompiler: De-deprecate until more use cases have alternatives We deprecated this module in commit v3.5.0-rc1~295^2 (CMakeForceCompiler: Deprecate this module and its macros, 2015-10-19) in order to determine whether anyone still has use cases that require it. Indeed we still need to provide a way to work with toolchains that cannot link binaries without special flags. Remove the deprecation warnings until we can provide an alternative to the module for this use case. | 17 February 2016, 14:15:18 UTC |
| 229a5bc | Brad King | 12 February 2016, 16:25:36 UTC | Merge branch 'fix-cmake_parse_arguments-expansion' into release | 12 February 2016, 16:25:36 UTC |
| c8c45a2 | Dimitar Yordanov | 12 February 2016, 12:21:12 UTC | cmake_parse_arguments: Restore ;-list argument flattening The re-implementation in commit v3.5.0-rc1~116^2~1 (CMakeParseArguments: replace by native cmake_parse_arguments command, 2015-12-05) introduced a regression when parsing the ARGN arguments with cmake_parse_arguments. The original implementation used foreach(currentArg ${ARGN}) to iterate over input arguments. This flattened ;-lists within the arguments whether they were quoted or not. Fix our new implementation to preserve this behavior and add a test case to cover it. Signed-off-by: Dimitar Yordanov <dimitar.yordanov@sap.com> Signed-off-by: Matthias Maennich <matthias.maennich@sap.com> | 12 February 2016, 16:19:40 UTC |
| 2410a20 | Brad King | 12 February 2016, 15:22:31 UTC | Merge branch 'cmake-gui-reset-generator' into release | 12 February 2016, 15:22:31 UTC |
| da490e1 | Brad King | 12 February 2016, 15:15:11 UTC | cmake-gui: Fix cmState initialization when changing generators (#15959) Refactoring in commit v3.3.0-rc1~29^2~1 (cmState: Host some state from the cmGlobalGenerator, 2015-05-24) moved storage of some generator traits over to cmState. However, it accidentally removed initialization of the values from the cmGlobalGenerator constructor. This is needed because generator subclasses update the settings in their constructors. Since a single cmState instance is shared across multiple build trees by cmake-gui, initializing the values in its constructor is not enough. Fix this by restoring the needed initializations to the cmGlobalGenerator constructor. | 12 February 2016, 15:21:00 UTC |
| 3e966ef | Brad King | 11 February 2016, 14:58:55 UTC | Merge branch 'doc-xcode-escaping-fix' into release | 11 February 2016, 14:58:55 UTC |
| 878632c | Brad King | 11 February 2016, 14:52:37 UTC | Help: Add release note about Xcode escaping fix (#15969) The fix in commit v3.5.0-rc1~84^2 (Xcode: Escape all backslashes in strings, 2015-12-27) is a change in behavior that can break existing projects that worked around the inconsistency with other generators. Add a release note to call attention to this change in behavior. | 11 February 2016, 14:53:34 UTC |
| 8d1b37a | Brad King | 10 February 2016, 14:23:57 UTC | CMake 3.5.0-rc2 | 10 February 2016, 14:23:57 UTC |
| b162dd9 | Brad King | 09 February 2016, 18:26:50 UTC | Merge branch 'curl-pre-7.21.5' into release | 09 February 2016, 18:26:50 UTC |
| 1ea55ac | Brad King | 09 February 2016, 18:20:39 UTC | cmCurl: Fix compilation with system curl versions prior to 7.21.5 This version introduced CURLE_NOT_BUILT_IN which we have used since commit v3.4.0-rc1~211^2~4 (cmCurl: Tolerate lack of CURLOPT_CAPATH support, 2015-08-12). For older versions, just define the name to the then-unused error code so that we can compile. | 09 February 2016, 18:24:19 UTC |
| 5b06896 | Brad King | 09 February 2016, 15:35:53 UTC | Merge branch 'wix-prevent-nsis-overwrite' into release | 09 February 2016, 15:35:53 UTC |
| a12b0f1 | Nils Gladitz | 07 February 2016, 19:25:56 UTC | CMake: Prevent WiX installations over existing NSIS installations Use a custom action to look for Uninstall.exe in the user selected installation prefix. Its presence indicates a previous NSIS installation. Inform the user and request manual resolution of the issue. | 09 February 2016, 15:28:57 UTC |
| 0570b4e | Brad King | 08 February 2016, 18:23:45 UTC | Merge branch 'fix-target-lookup-performance-regression' into release | 08 February 2016, 18:23:45 UTC |
| 9b7d587 | Brad King | 08 February 2016, 17:50:56 UTC | Improve internal generator target structure lookup In commit v3.5.0-rc1~272^2~6 (cmGlobalGenerator: Add FindGeneratorTarget API, 2015-10-25) a lookup was implemented via linear search. Replace it with an efficient data structure. Suggested-by: Stephen Kelly <steveire@gmail.com> | 08 February 2016, 18:08:11 UTC |
| 6cbf6a5 | Brad King | 08 February 2016, 17:37:47 UTC | Fix internal target lookup performance regression Refactoring in commit v3.5.0-rc1~272^2~13 (cmGlobalGenerator: Remove direct storage of targets, 2015-10-25) replaced an efficient data structure mapping from target name to cmTarget instance with a linear search. Lookups through cmGlobalGenerator::FindTarget are done a lot. Restore the efficient mapping structure with a name indicating its purpose. Reported-by: Bartosz Kosiorek <gang65@poczta.onet.pl> | 08 February 2016, 18:08:11 UTC |
| 656bf0d | Brad King | 08 February 2016, 15:46:42 UTC | Merge branch 'fix-install-EXPORT-crash' into release | 08 February 2016, 15:46:42 UTC |
| a1ad098 | Brad King | 08 February 2016, 15:44:43 UTC | Tests: Avoid OS X 10.5 limitation warning in RunCMake.install test The EXPORT-OldIFace test case uses install(TARGETS) and so generates a warning: CMake Warning in CMakeLists.txt: WARNING: Target "foo" has runtime paths which cannot be changed during install. To change runtime paths, OS X version 10.6 or newer is required. Therefore, runtime paths will not be changed when installing. CMAKE_BUILD_WITH_INSTALL_RPATH may be used to work around this limitation. Set CMAKE_BUILD_WITH_INSTALL_RPATH to avoid the warning since we do not need to run the binaries from the build tree anyway. | 08 February 2016, 15:44:43 UTC |
| 2a768f8 | Brad King | 08 February 2016, 15:35:59 UTC | Merge branch 'test-ctest_submit-update' into release | 08 February 2016, 15:35:59 UTC |
| 98d6d8f | Brad King | 08 February 2016, 15:35:51 UTC | Merge branch 'install-man-conditionally' into release | 08 February 2016, 15:35:51 UTC |
| 024c4ea | Brad King | 08 February 2016, 15:35:45 UTC | Merge branch 'fix-doc-typos' into release | 08 February 2016, 15:35:45 UTC |
| 52a81d6 | Brad King | 08 February 2016, 15:35:41 UTC | Merge branch 'ExternalProject-build-config-compat' into release | 08 February 2016, 15:35:41 UTC |
| cb40969 | Brad King | 08 February 2016, 15:35:30 UTC | Merge branch 'fix-Fortran-module-in-subdir' into release | 08 February 2016, 15:35:30 UTC |
| a3b91d1 | Horst Kronstorfer | 08 February 2016, 11:55:25 UTC | Help: Fix command specification for cmake_minimum_required Implementation indicates that at least two components of VERSION must be specified (see Source/cmCMakeMinimumRequired.cxx.) Therefore the minor version is not optional. | 08 February 2016, 14:52:56 UTC |
| d8c9080 | Paul Wilkinson | 07 February 2016, 20:46:27 UTC | Help: Fix mistake in cmake-buildsystem(7) example The COMPATIBLE_INTERFACE_NUMBER_MAX example now sets INTERFACE_CONTAINER_SIZE_REQUIRED on lib1Version2 and lib1Version3. Previously set it on lib1Version2 twice and never on lib1Version3. | 08 February 2016, 14:51:37 UTC |
| 8282547 | Brad King | 08 February 2016, 14:37:24 UTC | Install ccmake.1 and cmake-gui.1 conditionally with their tools (#15957) | 08 February 2016, 14:38:18 UTC |
| 2859d9e | Orion Poplawski | 08 February 2016, 14:22:54 UTC | Tests: Extend ctest_submit host lookup failure matching (#15958) Match this message: Could not resolve host: -no-site-; Name or service not known ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | 08 February 2016, 14:25:21 UTC |
| 1b9d15c | Brad King | 05 February 2016, 19:18:01 UTC | ExternalProject: Be compatible with projects setting CMAKE_CFG_INTDIR Since commit v3.5.0-rc1~32^2~1 (ExternalProject: Simplify `cmake --build` configuration passing, 2016-01-19) we use the `$<CONFIG>` generator expression to generate the `cmake --build . --config <config>` value for the default BUILD_COMMAND instead of the CMAKE_CFG_INTDIR placeholder value provided by multi-config generators. However, some projects have been abusing the old implementation detail by setting CMAKE_CFG_INTDIR themselves to get a specific configuration. Those projects should be updated to set their own BUILD_COMMAND to get non-default behavior. Meanwhile we can be compatible with their existing releases by detecting when CMAKE_CFG_INTDIR is not a generator-provided placeholder and using its value instead. | 05 February 2016, 19:43:16 UTC |
| 47460f3 | Brad King | 04 February 2016, 16:45:54 UTC | install(EXPORT): Fix crash on target in another directory Refactoring merged by commit v3.5.0-rc1~299 (Merge topic 'use-generator-target', 2015-10-20) in and around commit v3.5.0-rc1~299^2~13 (cmExportSet: Store a cmGeneratorTarget, 2015-10-17) changed export sets to delay looking up actual targets and stores only their names. However, in InstallCommand::HandleExportMode we need to lookup targets immediately to check them for EXPORT_LINK_INTERFACE_LIBRARIES. The check was accidentally made local to the current directory, so if an export set contains a target from another directory the lookup fails and CMake crashes. Fix the check to look up the target name globally, and tolerate when no target is found just in case. Reported-by: Kelly Thompson <kgt@lanl.gov> | 05 February 2016, 14:45:16 UTC |
| e86383e | Brad King | 05 February 2016, 14:40:13 UTC | Tests: Use newer policy settings in RunCMake.install test In particular, avoid CMP0042 warnings on OS X. | 05 February 2016, 14:44:26 UTC |
| c5eb21b | Brad King | 05 February 2016, 13:55:15 UTC | Fix dependency scanning configuration in subdirectories Refactoring in commit v3.5.0-rc1~347^2~2 (Set the current dirs on the snapshot before creating the cmMakefile) accidentally changed the source and binary directories configured in `cmake -E cmake_depends` for use during dependency scanning. This can cause the wrong directory information to be loaded. It also breaks Fortran module dependency scanning for modules provided by targets in subdirectories that do not have Fortran_MODULE_DIRECTORY set. Fix the dependency scanning directory configuration and add a test to cover the Fortran module case in which the breakage was observed. Reported-by: Kelly Thompson <kgt@lanl.gov> | 05 February 2016, 14:26:44 UTC |
| 8a8d22c | Brad King | 02 February 2016, 13:37:05 UTC | CMake 3.5.0-rc1 version update | 02 February 2016, 13:37:05 UTC |
| 021a74a | Brad King | 02 February 2016, 13:34:47 UTC | Help: Drop development topic notes to prepare release Release versions do not have the development topic section of the CMake Release Notes index page. | 02 February 2016, 13:34:47 UTC |
| a5a5a68 | Brad King | 02 February 2016, 13:33:25 UTC | Merge topic 'doc-3.5-relnotes' ad701d9f Help: Organize and revise 3.5 release notes 377a12b2 Help: Consolidate 3.5 release notes | 02 February 2016, 13:33:25 UTC |
| 570e84b | Brad King | 02 February 2016, 13:33:23 UTC | Merge topic 'remove-stray-semicolon' ccb2d5c0 cmAlgorithms.h: remove superfluous semicolon after method | 02 February 2016, 13:33:23 UTC |
| f8e5e5b | Brad King | 02 February 2016, 13:33:20 UTC | Merge topic 'fix-CMAKE_MATCH-self-match' 6ffc4323 cmConditionEvaluator: Fix matching of `CMAKE_MATCH_*` values (#15944) | 02 February 2016, 13:33:20 UTC |
| 6a230df | Kitware Robot | 02 February 2016, 05:01:05 UTC | CMake Nightly Date Stamp | 02 February 2016, 05:01:05 UTC |
| ad701d9 | Brad King | 01 February 2016, 18:38:00 UTC | Help: Organize and revise 3.5 release notes Add section headers similar to the 3.4 release notes and move each individual bullet into an appropriate section. Revise a few bullets. | 01 February 2016, 18:38:36 UTC |
| 377a12b | Brad King | 01 February 2016, 17:47:27 UTC | Help: Consolidate 3.5 release notes Move all development release notes into a new version-specific document: tail -q -n +3 Help/release/dev/* > Help/release/3.5.rst git rm -- Help/release/dev/* except the sample topic: git checkout HEAD -- Help/release/dev/0-sample-topic.rst Reference the new document from the release notes index document. Add a title and intro sentence to the new document by hand. | 01 February 2016, 17:50:43 UTC |
| ccb2d5c | Christoph Grüninger | 29 January 2016, 21:16:03 UTC | cmAlgorithms.h: remove superfluous semicolon after method | 01 February 2016, 15:47:25 UTC |
| adc3d12 | Brad King | 01 February 2016, 15:43:57 UTC | Merge topic 'doc-cmake-developer-typo' 6f83db1c Help: Fix typo in `cmake-developer(7)` manual | 01 February 2016, 15:43:57 UTC |
| 5ee96fc | Brad King | 01 February 2016, 15:43:54 UTC | Merge topic 'FindGit-updates' fa78ee97 FindGit: Improve documentation formatting facfb52c FindGit: Document Git_FOUND, unset internal var | 01 February 2016, 15:43:54 UTC |
| c022b6f | Brad King | 01 February 2016, 15:43:51 UTC | Merge topic 'clarify-add_custom_command-TARGET-scope' d257d681 add_custom_command: Clarify error when TARGET is out of scope (#15681) 4d53e0a7 Help: Clarify `add_custom_command(TARGET)` scope (#15681) 8c615af4 Help: Clarify policy `CMP0040` documentation (#15681) 63c5808f Help: Clarify scope of `if(TARGET)` expression a336e438 Help: Improve markup in `if` command documentation 88968265 Help: Improve markup in `get_target_property` documentation | 01 February 2016, 15:43:51 UTC |
| 6f83db1 | Prayag Verma | 31 January 2016, 19:03:56 UTC | Help: Fix typo in `cmake-developer(7)` manual Fix spelling mistake `sytem` => `system`. | 01 February 2016, 15:36:25 UTC |
| 6ffc432 | Brad King | 01 February 2016, 14:49:08 UTC | cmConditionEvaluator: Fix matching of `CMAKE_MATCH_*` values (#15944) While evaluating `if(MATCHES)` we get a `const char*` pointer to the string to be matched. On code like if(CMAKE_MATCH_COUNT MATCHES "Y") the string to be matched may be owned by our own result variables. We must move the value to our own buffer before clearing them. Otherwise we risk reading freed storage. | 01 February 2016, 15:05:10 UTC |
| e18d0df | Kitware Robot | 01 February 2016, 05:01:03 UTC | CMake Nightly Date Stamp | 01 February 2016, 05:01:03 UTC |
| 13b4ef2 | Kitware Robot | 31 January 2016, 05:01:03 UTC | CMake Nightly Date Stamp | 31 January 2016, 05:01:03 UTC |
| f270404 | Kitware Robot | 30 January 2016, 05:01:03 UTC | CMake Nightly Date Stamp | 30 January 2016, 05:01:03 UTC |
| 76a51df | Kitware Robot | 29 January 2016, 05:01:04 UTC | CMake Nightly Date Stamp | 29 January 2016, 05:01:04 UTC |
| d257d68 | Brad King | 28 January 2016, 15:12:26 UTC | add_custom_command: Clarify error when TARGET is out of scope (#15681) The add_custom_command(TARGET) signature only works for targets defined in the current directory. Clarify this in the error message when the target exists but was defined elsewhere. Inspired-by: Bartosz Kosiorek <gang65@poczta.onet.pl> | 28 January 2016, 15:33:26 UTC |
| 4d53e0a | Bartosz Kosiorek | 28 January 2016, 09:52:15 UTC | Help: Clarify `add_custom_command(TARGET)` scope (#15681) | 28 January 2016, 15:13:27 UTC |
| 8c615af | Bartosz Kosiorek | 28 January 2016, 09:52:15 UTC | Help: Clarify policy `CMP0040` documentation (#15681) State explicitly that the target must be defined in the current directory. While at it, improve markup formatting. | 28 January 2016, 15:13:18 UTC |
