GitLab

Brad King authored Feb 18, 2016 and Kitware Robot committed Feb 18, 2016

d7c6b710 Merge branch 'backport-doc-install-component-association' into doc-install-component-association
c978223c Help: Clarify install(TARGETS) INCLUDES DESTINATION option
70f2708f Help: Clarify install(TARGETS) INCLUDES DESTINATION option

Brad King authored Feb 18, 2016 and Kitware Robot committed Feb 18, 2016

beaa4fa5 CMakeForceCompiler: De-deprecate until more use cases have alternatives

Brad King authored Feb 18, 2016 and Kitware Robot committed Feb 18, 2016

87f44b75 Fix export of STATIC library PRIVATE non-target dependencies

Brad King authored Feb 18, 2016 and Kitware Robot committed Feb 18, 2016

1911cda0 FindCUDA: Fix regression under Visual Studio generators

Brad King authored Feb 18, 2016 and Kitware Robot committed Feb 18, 2016

9beb2744 Automoc: Fix support of files with the same name (#12873)

Since commit v3.5.0-rc1~47^2 (FindCUDA: Support special characters in
path, 2016-01-15) our add_custom_command calls use VERBATIM so that
CMake will automatically quote special characters correctly.  However,
this breaks the special `$(VCInstallDir)` placeholder used with Visual
Studio generators.  Since we do not support preservation of such
placeholders with VERBATIM (see issue #15001

) we must fall back to not
using VERBATIM when the placeholder is used.

A better fix would be to stop using `$(VCInstallDir)` and use the value
of `CMAKE_${CUDA_C_OR_CXX}_COMPILER` instead, but that will require
additional semantic and documentation changes.  For now simply fix the
regression with the above approach.
Reported-by: Stephen Sorley <Stephen.Sorley@jhuapl.edu>

In commit v3.5.0-rc1~43^2 (Fix export of STATIC library PRIVATE
dependencies with CMP0022 NEW, 2016-01-15) we taught
target_link_libraries to generate `$<LINK_ONLY:$<TARGET_NAME:dep>>` in
INTERFACE_LINK_LIBRARIES instead of `$<LINK_ONLY:dep>` so that `dep` can
be recognized as a target name and updated during export.  However, this
approach does not work when `dep` is just a plain library name and not a
target because `$<TARGET_NAME:...>` requires the name of a reachable
target.

Since we do not know during target_link_libraries whether the name will
correspond to a reachable target or not, we cannot inject the
`$<TARGET_NAME:...>` expression.  Revert this change and solve the
original problem instead by teaching the export logic to recognize and
update target names directly in `$<LINK_ONLY:...>` expressions.
Reported-by: Ben Boeckel <ben.boeckel@kitware.com>

Brad King authored Feb 17, 2016 and Kitware Robot committed Feb 17, 2016

bf643286 FindwxWidgets: Resolve Cygwin/MSYS paths to Windows paths

Brad King authored Feb 17, 2016 and Kitware Robot committed Feb 17, 2016

bb7a41ab FindProtobuf: check version

Brad King authored Feb 17, 2016 and Kitware Robot committed Feb 17, 2016

184da3f4 CodeBlocks: improve support for different compilers

The option does not actually participate in argument groups like the
others because it does not actually install anything.  Fix the order
in the documentation accordingly.
Reported-by: Daniel Wirtz <daniel.wirtz@simtech.uni-stuttgart.de>

The option does not actually participate in argument groups like the
others because it does not actually install anything.  Fix the order
in the documentation accordingly.
Reported-by: Daniel Wirtz <daniel.wirtz@simtech.uni-stuttgart.de>

We deprecated this module in commit v3.5.0-rc1~295^2
(CMakeForceCompiler: Deprecate this module and its macros, 2015-10-19)
in order to determine whether anyone still has use cases that require
it.  Indeed we still need to provide a way to work with toolchains that
cannot link binaries without special flags.  Remove the deprecation
warnings until we can provide an alternative to the module for this use
case.

Wayne Stambaugh authored Feb 14, 2016 and Brad King committed Feb 17, 2016

We use `sh wx-config` to launch the `wx-config` tool so that it can run
even on Windows.  Since it is always a shell script its output may use
POSIX paths even on Windows.  Use `cygpath` to convert to Windows paths.

Melven Roehrig-Zoellner authored Feb 12, 2016 and Brad King committed Feb 16, 2016

More elaborate selection of the `compiler` tag in the generated
CodeBlocks project file:

* Fortran language support

* support for several of the predefined compilers recognized by
  CodeBlocks (16.01)

Antonio Perez Barrero authored Feb 12, 2016 and Brad King committed Feb 16, 2016

Check found libraries version to match user required version.

Protobuf compiler executable version is checked to be aligned with found
libraries, raising a warning message otherwise.

Brad King authored Feb 16, 2016 and Kitware Robot committed Feb 16, 2016

da490e11 cmake-gui: Fix cmState initialization when changing generators (#15959)

Brad King authored Feb 16, 2016 and Kitware Robot committed Feb 16, 2016

c8c45a2c cmake_parse_arguments: Restore ;-list argument flattening

Brad King authored Feb 16, 2016 and Kitware Robot committed Feb 16, 2016

7c7efd1e CPack/RPM support for upper cased component variables

Brad King authored Feb 16, 2016 and Kitware Robot committed Feb 16, 2016

326ad994 Tests: fix GenerateExportHeader directory definitions

Brad King authored Feb 16, 2016 and Kitware Robot committed Feb 16, 2016

46fa9583 Ninja: Fix non-determinism in generated target dependency order (#15968)

CPACK_* variables expect component name in upper case.
CPACK_RPM_* variables expected component name to be
in same case as component name.
This patch adds support for CPACK_RPM_* variables with
upper case component names to match the convention with
CPACK_* variables and also preserves same case component
names for back compatibility.

There's no need to stringify the values, but instead just pass in
strings. The core problem is that the path may have tokens which are
replaced by the preprocessor which causes an invalid path to be used.