- 28 Oct, 2016 1 commit
-
-
Kitware Robot authored
-
- 27 Oct, 2016 7 commits
-
-
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
-
- 26 Oct, 2016 8 commits
-
-
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.
-
68e7250a Features: Fix cxx_right_angle_brackets compiler feature test
-
Brad King authored
Issue: #16384
-
Daniel Pfeifer authored
-
Kitware Robot authored
-
- 25 Oct, 2016 15 commits
-
-
The clang-format pass in commit v3.6.0-rc1~54^2~1 (Revise C++ coding style using clang-format, 2016-05-16) changed the template right angle brackets from `>>` to `> >`, which defeats the purpose of this test. Change it back and exclude this content from formatting.
-
MSBuild interprets the `.vcxproj` content based on the `PlatformToolset` setting, so our reverse mapping needs to be based on that setting too. For VS 2010 and above, choose the flag map to match the toolset name rather than the generator VS version. Issue: #16153
-
Brad King authored
-
Move `Get*FlagTable` methods to the global generator and have each VS generator version pre-populate its default flag table.
-
Brad King authored
* upstream-KWSys: KWSys 2016-10-23 (b630d2f5)
-
Code extracted from: http://public.kitware.com/KWSys.git at commit b630d2f5575be7d70c214bfffc57aaf5069c6369 (master). Upstream Shortlog ----------------- Dāvis Mosāns (1): b630d2f5 ConsoleBuf: Check for actual console with GetConsoleMode
-
Brad King authored
-
c15dc197 Introduce CM_UNORDERED_SET
-
15aa814b Remove cmObject.h and cmTypeMacro.h
-
881585f9 Intel: Fix compiler extension flags on Windows
-
9f1429e2 Sublime: Update generated diagnostic matching expression for MSVC
-
9b8dc79c cmake-server: Change message wrapper to avoid ambiguity with content
-
Kitware Robot authored
-
- 24 Oct, 2016 9 commits
-
-
Daniel Pfeifer authored
Avoid duplicating switch among std::unordered_set, cmsys::hash_set, and std::set.
-
Daniel Pfeifer authored
-
Brad King authored
-
Brad King authored
-
Brad King authored
Change our message wrapper from [== CMake Server ==[ ... ]== CMake Server ==] to [== "CMake Server" ==[ ... ]== "CMake Server" ==] to guarantee that no JSON content can ever contain the ending string (because it would be encoded as `]== \"CMake Server\" ==]`).
-
Brad King authored
The extension flags enabled by commit v3.6.0-rc1~120^2~1 (Features: Record standard flags for Intel C/C++ on Windows, 2016-04-18) of the form `-Qstd=gnu++11` are not supported by the Intel C/C++ Compiler for Windows. Fall back to using the non-extension form of the flags. Issue: #16384
-
Update the generated `file_regex` to match MSVC-style messages in addition to the GCC-style messages already matched. Use non-capturing sub-patterns to tolerate the differences in message formats while still capturing the four pieces of information in proper group numbers (file name, line number, column number, message). Closes: #16375
-
Brad King authored
-
Brad King authored
Add `-fPIE -pie` to the default executable link flags when `CMAKE_POSITION_INDEPENDENT_CODE` is enabled. This is required by Android 16 and above for executables to run on the device. Closes: #16382
-