- Mar 16, 2017
-
-
Chuck Atkins authored
-
Chuck Atkins authored
-
- Feb 03, 2017
-
-
37ed860a GNU C++: record that -fvisibility-inlines-hidden is available since 4.0 94a8ee6f GNU C: record that C99 is available since at least 3.4 940bf6a4 Tests/Module/WCDH: only use -Werror=undef compiler flag if actually supported f26ca5a1 Tests/Module/WCDH: write multi_file_compiler_detection.h before using it
-
Kitware Robot authored
-
- Feb 02, 2017
-
-
Rolf Eike Beer authored
-
Rolf Eike Beer authored
-
Rolf Eike Beer authored
This was broken in commit 98e6d1e5 (Tests/Module/WCDH: make it work with only C features defined) when all C tests were made accessible even if no C++ features are available, but the header was only created if C++ features are available. Fix it by creating the header unconditionally before any checks on the available features.
-
645dd3ca FindCUDA: Fix typo in CUDA_DETECT_INSTALLED_GPUS doc string
-
-
be3727bf Help: Fix language standard link text in cmake-compile-features(7)
-
Brad King authored
Include each language name in the text of the link to its standards property.
-
88c4576b FindGSL: Fix gl_version.h extraction regex
-
Kitware Robot authored
- Feb 01, 2017
-
-
Fix the regex to match versions with only two digits, such as `2.3`.
-
Brad King authored
-
Brad King authored
-
1679fecb CompileFeatures Test: make sure the target "CompileFeatures" is always defined 98e6d1e5 Tests/Module/WCDH: make it work with only C features defined c8703e9d WCDH: optionally omit error code for unknown compilers or compiler versions 0de9c398 WCDH: add macro to write simple replacement defines
-
c9ee05d8 FortranCInterface: Fix support for VS with Intel toolset
-
5d70894d Features: Update version of Intel Compiler on Windows supporting C 11
-
f3619bbc Help: Fix typo in <pkg>_NOT_FOUND_MESSAGE example in cmake-packages(7)
-
9f3e812f Help: Extend documented purpose of cmake-developer(7) manual
-
Brad King authored
Issue: #16616
-
Brad King authored
The Intel Compiler 15.0.0 on Windows does not support `-Qstd=c11`. Bump our version requirement to 16 to use that flag.
-
Brad King authored
When using a Visual Studio generator with an Intel toolset, such as -T "Intel C++ Compiler XE 14.0" the generated FortranCInterface mangling detection project may fail to build due to `devenv` not working with the `/project ALL_BUILD` option. This seems to be a bug in `devenv` or the Intel VS integration. Work around the problem by building with `/project FortranCInterface` instead. We only need to build this executable and its dependencies within the detection test project anyway. Fixes: #16519
-
Kitware Robot authored
-
- Jan 31, 2017
-
-
Brad King authored
The `git config` format is cleaner than a bash script and is also supported by our `hooks` branch to specify CMake-specific hooks.
-
Brad King authored
Add a version number to the `SetupForDevelopment.sh` script and use a pre-commit hook to check when it changes.
-
435cebaa VS: Fix CSharp compiler identification for VS 2017
-
97d61562 FindBoost: unset cache variables if the lib dir changes
-
5181f1f8 Tests: make tests pass with SOURCE_DATE_EPOCH set
-
4dde0bc8 VS: Fix WINDOWS_EXPORT_ALL_SYMBOLS for external objects
-
071f8e78 Apple: Add support for static frameworks d525754e Xcode: Refactor RunCMake.Framework test to prepare for static frameworks 45405f00 Xcode: Ignore Xcode project warning until issue is fixed 50e1c105 Makefile: For static libraries remove only the "real" lib before creating 8643ca75 Makefile: Re-order list of files to clean
-
050bb41c Tell Git not to export the GitSetup directory d6108c87 GitSetup: Tell Git not to export .gitattributes 3642d657 Merge branch 'upstream-GitSetup' into developer-setup 7e5ef9ca GitSetup 2016-12-13 (cd5ada6d) a6fda7bf Merge branch 'upstream-GitSetup' into developer-setup a2d393d6 Add script to update GitSetup from upstream c7b846ed GitSetup 2012-04-26 (b7daff9b)
-
The CSharp compiler for VS 2017 has moved from `MSBuildTools` to `RoslynTargets`. Account for both locations giving priority to the `MSBuildTools` location.
-
Closes: #16432
-
Kitware Robot authored
-
- Jan 30, 2017
-
-
Brad King authored
The `Utilities/GitSetup` directory is useful only in Git work trees and so does not need to be distributed with source tarballs.
-