- Dec 13, 2016
-
-
-
Kitware Robot authored
-
- Dec 12, 2016
-
-
45054119 Help: Document CUDA_STANDARD and related properties
-
b932cd42 clang-tidy: apply misc-redundant-expression fixes 88da3d68 clang-tidy: apply misc-suspicious-string-compare fixes 58c66393 clang-tidy: apply readability-static-definition-in-anonymous-namespace fixes 85bfddda clang-tidy: apply readability-redundant-control-flow fixes 2988abd9 clang-tidy: apply modernize-use-bool-literals fixes a74e6893 clang-tidy: apply readability-redundant-string-init fixes cac529dd clang-tidy: apply performance-faster-string-find fixes 7c9db8f8 clang-tidy: apply performance-unnecessary-value-param fixes
-
Brad King authored
-
-
-
-
-
-
-
-
-
Kitware Robot authored
- Dec 11, 2016
-
-
Kitware Robot authored
-
- Dec 10, 2016
-
-
Kitware Robot authored
-
- Dec 09, 2016
-
-
Brad King authored
-
c3b6b5ba FindBoost: Add support for VS 2017
-
Brad King authored
Make the return types of the extern function declared in `main.cpp` match those in the method implementations.
-
Brad King authored
Since commit v3.7.0-rc1~392^2 (Honor CMAKE_<LANG>_FLAGS[_<CONFIG>]_INIT set in toolchain files, 2016-07-05) our convention is to initialize compiler flag variables via `string(APPEND)` rather than `set()`. Fix the convention for `CMAKE_CUDA_FLAGS[_<CONFIG>]_INIT`.
-
-
Brad King authored
-
Brad King authored
Call sites of `ExpandRuleVariables` are now responsible for inserting the `RULE_LAUNCH_{COMPILE,LINK,CUSTOM}` values in rule command lines. Audit all call sites and add a comment to each one that does not insert a launcher to explain why.
-
Brad King authored
Refactoring in commit 425cd167 (cmLocalGenerator: Remove the launcher from RuleVariables, 2016-10-09) accidentally broke Makefile generator handling of `RULE_LAUNCH_COMPILE`. Responsibility moved from `ExpandRuleVariables` to its call sites, and the Makefile generator call site for compilations was not properly updated. Fix it now.
-
Kitware Robot authored
-
- Dec 08, 2016
-
-
Brad King authored
-
e438693e VS: Teach option map IsDebug() method about C# projects
-
e326d8cf CPack/DEB shlibdep options depend on file utility
-
Brad King authored
-
Kitware Robot authored
-
- Dec 07, 2016
-
-
Missing or missconfigured file utility should not skip adding dependencies. Instead it should print out a fatal error message. Fixes #16486
-
-
Brad King authored
-
Brad King authored
Merge branch 'vs-fix-standalone-Windows7.1SDK-toolset' into vs-fix-standalone-Windows7.1SDK-toolset-for-master
-
Brad King authored
Since commit v3.7.0-rc1~142^2~1 (VS: Explicitly default to v100 toolset in Visual Studio 2010, 2016-07-21) we prefer to always set a platform toolset explicitly so that `CMAKE_VS_PLATFORM_TOOLSET` can be reported. However, the `v100` default for the VS 10 generator is not appropriate for all environments. We fixed support for VS 2010 Express Edition in commit v3.7.0-rc1~142^2 (VS: Do not default to missing v100 64-bit toolset on VS 2010 Express, 2016-09-09). Fix support for the standalone Windows7.1SDK toolset environment by recognizing the `PlatformToolset` environment variable that it sets to `Windows7.1SDK` and using this as our default toolset instead. Closes: #16483
-