- Nov 01, 2016
-
-
f2de7079 FindMatlab: Fix typo in matlab_add_unit_test implementation
-
e29f33cd FindMatlab: Add support for Matlab 2016b (9.1)
-
95805d72 Sublime: Add option to specify env vars for the .sublime-project
-
353f6362 Ninja: Fix POST_BUILD noop on Windows
-
Kitware Robot authored
-
- Oct 31, 2016
-
-
Kitware Robot authored
-
- Oct 30, 2016
-
-
Daniel Pfeifer authored
-
Daniel Pfeifer authored
-
Daniel Pfeifer authored
-
Kitware Robot authored
-
- Oct 29, 2016
-
-
Kitware Robot authored
-
- Oct 28, 2016
-
-
Brad King authored
Use `cd .` instead of `:` in a Windows shell. Closes: #16393
-
Fix typo in variable used to communicate between matlab_add_unit_test and its helper script MatlabTestsRedirect.cmake that was introduced in commit v3.7.0-rc1~116^2 (FindMatlab: Extend matlab_add_unit_test to run arbitrary test code, 2016-08-30).
-
Brad King authored
-
This allows users to specify different genex-based compile flags for each file in a target, e.g. compiling just a single file with `Od/Ox` in release builds on Visual Studio.
-
-
Brad King authored
-
Brad King authored
-
Tobias Hunger authored
-
Kitware Robot authored
-
- Oct 27, 2016
-
-
Catch more problematic input during handshake and report failure. These were caught before when trying to configure, but it is way better to get these reports early.
-
Create a `CMAKE_SUBLIME_TEXT_2_ENV_SETTINGS` variable to control addition of env vars in the `.sublime-project`. Closes: #16387
-
Brad King authored
Since this compiler always defines `__cplusplus` to `1` we need to use `_MSC_VER`, `__INTEL_CXX11_MODE__`, and the feature test macro named `__cpp_aggregate_nsdmi` to detect C++11 and C++14 modes. With no `-Qstd=` flag this compiler defaults to C++98 plus a subset of C++11/C++14 features needed to be compatible with MSVC. We pretend it is plain C++98 and add a `-Qstd=` flag whenever needed for C++11 or above features even if they would happen to be available in MSVC-mode. Closes: #16384
-
Brad King authored
The Intel 16 and 17 compilers define feature test macros of the form `__cpp_<feature>`. Use them where possible to detect corresponding features.
-
Brad King authored
-
Brad King authored
The change in commit 05e05cd2 (Intel: Fix compiler C++98 standard flag on Windows, 2016-10-26) was wrong. The Intel C++ Compiler for Windows does not support either `-Qstd=c++98` or `-Qstd=gnu++98`. Simply remove both flags for this compiler and use no options at all to achieve this mode. Issue: #16384
-
e81c323d Include necessary headers in commands
-
335a29cb Enable Unicode output to Windows consoles
-
05e05cd2 Intel: Fix compiler C++98 standard flag on Windows
-
554b4f90 Features: Record features for Intel C++ 17 on UNIX
-
0caca40f VS: Fix use of `Windows7.1SDK` 64-bit toolset with VS 2010 Express
-
Brad King authored
Refactoring in commit 584ab528 (VS: Add internal API to get platform toolset as string, 2016-10-18) accidentally changed the semantics of the original `cmGlobalVisualStudio10Generator::GetPlatformToolset` implementation to return a pointer to an empty string instead of `nullptr` when no toolset is configured. This broke cases that tested for `nullptr` to detect the lack of any specific toolset, such as the call in `Find64BitTools`. Restore the `nullptr` return in this case.
-
Kitware Robot authored
-
- Oct 26, 2016
-
-
Brad King authored
The Intel C++ Compiler for Windows does not support the `-Qstd=c++98` flag but does support `-Qstd=gnu++98`. Issue: #16384
-
Dāvis Mosāns authored
Use KWSys ConsoleBuf to replace the `streambuf` on `std::cout` and `std::cerr` so that process output can be encoded correctly for display in a Windows console.
-