- Sep 23, 2015
-
-
-
b761e90d CPack: remove accidental changes
-
d1375851 Project: Don't require computed default dialect if compiler was forced.
-
Remove changes accidentally included in commit b58de9fe (CPack: allow packaging of empty directories, 2015-09-22).
-
Kitware Robot authored
-
- Sep 22, 2015
-
-
Stephen Kelly authored
Commit 7235334a (Project: Determine default language dialect for the compiler., 2015-09-15) introduced a mechanism to determine the default dialect used for the running compiler. If conditions in the <CompilerId>-<Lang>.cmake file are such that compile features for that version of the compiler should be supported, the _DEFAULT_STANDARD is set to the computed value. However, the CMakeForceCompiler module allows users to bypass execution of the compiler by CMake. In that case, do not set the _DEFAULT_STANDARD variable at all, which effectively disables the compile-features where the module is used. No compile features have ever been recorded where the module is used so no functionality is lost.
-
-
-
-
402bf096 CMP0064: Fix recorded version of introduction to be 3.4
-
17009189 Windows: Fix CMAKE_HOST_SYSTEM_VERSION on Windows >= 8 (#15674)
-
-
Brad King authored
When using "cmake --build ." or "MSBuild ALL_BUILD.vcxproj" to drive the build the dependencies in the .sln file are not considered. This means that ProjectReference elements in .vcxproj files are used to order targets. We must ensure that the ZERO_CHECK target is listed as the first dependency of every target so that when it causes regeneration of the build files then MSBuild has not yet loaded the updated files.
-
Brad King authored
Refactor cmGlobalVisualStudioGenerator::TargetCompare to store the name of the target that should come first instead of hard-coding "ALL_BUILD". Update client sites to specify "ALL_BUILD" when ordering for .sln files and an empty string otherwise (in cases when "ALL_BUILD" should not be encountered anyway).
-
Kitware Robot authored
-
- Sep 21, 2015
-
-
Domen Vrankar authored
-
-
Set policy CMP0065 to the value used in the calling project. Set the the value of CMAKE_ENABLE_EXPORTS if set in the calling project to initialize the target property appropriately.
-
This new policy restricts the addition of the shared library link flags to executables only when the ENABLE_EXPORTS property is set to True.
-
Brad King authored
This policy was added for CMake 3.4 but accidentally recorded as 3.3. Fix this and update the RunCMake.CMP0064 test WARN case accordingly.
-
-
-
-
-
-
bc2e54db Introduction of CPACK_VERBATIM_VARIABLES variable
-
-
-
-
-
According to GetVersionEx documentation: https://msdn.microsoft.com/en-us/library/windows/desktop/ms724451.aspx https://msdn.microsoft.com/en-us/library/windows/desktop/dn481241.aspx we must manifest each application to explicitly declare support for each version of Windows.
-
Kitware Robot authored
-
- Sep 20, 2015
-
-
If variable is set to TRUE, values of all variables prefixed with CPACK_ will be escaped so special characters such as dolar sign, quotes or foreward slash will not be lost. By default variable is treated as set to FALSE for back compatibility. The cpack_encode_variables macro is changed into a function to remove scope pollution. There should be no other effects.
-
Kitware Robot authored
-
- Sep 19, 2015
-
-
Kitware Robot authored
-
- Sep 18, 2015
-
-
Domen Vrankar authored
-
- Direct call to cmSystemTools::ComputeFileMD5 - Avoiding hashing symlinks - Tests
-
Stephen Kelly authored
Use it instead of the similar cmMakefile API. It is necessary to know that the Configure step is completely done, not just that one particular cmMakefile is finished configuring. Prior to commit 611220f7 (cmTarget: Use reliable test for CMP0024 and CMP0026 OLD., 2015-07-25), this was determined by checking whether cmGeneratorTargets exist yet, which happens after the Configure step.
-
Stephen Kelly authored
-
Stephen Kelly authored
This API is only called after configure-time.
-
