GitLab

Re-implement our internal `_HDF5_parse_compile_line` helper to process
command line arguments all at once and in order.  Otherwise the
libraries named by absolute path and those named by `-l` arguments are
not kept in order.

The new implementation will not handle separate arguments like
`-I /path/to/include/dir` but I have not seen the HDF5 compiler
wrappers produce this form.  If necessary the parsing loop can
be extended with a state variable to keep track of such pairs.

645dd3ca FindCUDA: Fix typo in CUDA_DETECT_INSTALLED_GPUS doc string

be3727bf Help: Fix language standard link text in cmake-compile-features(7)

Include each language name in the text of the link to its standards
property.

88c4576b FindGSL: Fix gl_version.h extraction regex

Fix the regex to match versions with only two digits, such as `2.3`.

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

3288ab0c Convert local hook configuration to a Git config file format
773df0e2 Add pre-commit hook to check whether SetupForDevelopment must re-run

Issue: #16616

The Intel Compiler 15.0.0 on Windows does not support `-Qstd=c11`.
Bump our version requirement to 16 to use that flag.

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

Fixes: #16616

The `git config` format is cleaner than a bash script and is also
supported by our `hooks` branch to specify CMake-specific hooks.

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

The `Utilities/GitSetup` directory is useful only in Git work trees
and so does not need to be distributed with source tarballs.

GitSetup upstream added an attribute to export `.gitattributes` so that
importing snapshots into the sources of other projects would bring along
the attributes.  However, we don't want to export them from CMake.  Drop
`.gitattributes` entries not relevant to CMake.

* upstream-GitSetup:
  GitSetup 2016-12-13 (cd5ada6d)

Code extracted from:

    https://gitlab.kitware.com/utils/gitsetup.git

at commit cd5ada6d5626da409d3ff108c341b9afd615803f (setup).

Code extracted from:

    https://gitlab.kitware.com/utils/gitsetup.git

at commit b7daff9b (setup).

Everything in there guards against unsupported compilers already, so no need to
skip the whole file if no features are defined. This in turn allows to have a
simpler fallback in case there is no C++ auto_type feature available.