Brad King authored 8 years ago and Kitware Robot committed 8 years ago

4cb5d335 VS: Place source-specific AdditionalOptions after target-wide flags

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

20cc76c9 CPackIFW: Update search to find QtIFW distributed with QtSDK

Konstantin Podsvirov authored 8 years ago and Brad King committed 8 years ago

Also avoid CMP0007 warnings.

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

ff3ccc1f FindHDF5: Restore pre-3.6 behavior of finding only C by default

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

baead1e2 Encoding: Remove option to use ANSI code page internally

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

9a8d758c Help: Document language standard meta-features
df252db1 Features: Test cycle diagnostic with language standard meta-feature
6d5fb0e0 Features: Test feature propagation with language standard meta-feature
a34b98a8 WCDH: Ignore language standard meta-features
b0996a3f Features: Add meta-features requesting awareness of a particular standard
8b6cc251 Features: Centralize per-compiler recording macros
2d23f7b2 Features: Do not record features on MSVC < 2010

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

b902f2a9 Features: Fix Intel cxx_attributes existence condition

This condition needs to follow the same pattern added in note `[1]` by
commit a5a3642f (Features: Port Intel CXX features to test macros where
possible, 2016-10-26).  It was accidentally left out of that commit.

Flags specified in the `COMPILE_FLAGS` source-file property should
be placed after those in target-wide properties so that those on
individual source files can override those on the whole target.
This is already done by most generators but was not implemented
correctly for VS 2010 and above.

Closes: #16400

The switch to use UTF-8 encoding has been defaulted to on for quite some
time since commit v3.2.0-rc1~116^2 (Encoding: Switch to use UTF-8
internally by default on Windows, 2014-12-26).

The `cxx_static_assert` feature may be available in C++ 98 mode of some
compilers or not available at all in others.  Intstead of using an
individual feature to test cyclic requirement of a feature requiring
C++ 11, use the `std_cxx_11` meta-feature that has exactly this meaning.

The `cxx_static_assert` feature may be available in C++ 98 mode of some
compilers or not available at all in others.  Intstead of using an
individual feature to test propagation of a feature requiring C++ 11,
use the `std_cxx_11` meta-feature that has exactly this meaning.

The `{c,cxx}_std_*` features are meant for use with
`target_compile_features` but do not make sense for use with
WriteCompilerDetectionHeader.  Filter them out of any requested list.

A common use case of `target_compile_features` is simply to specify that
the compiler should be run in a mode that is aware of e.g. C++11.  Some
projects simply specify a particular C++11-only feature to request this.
Provide a first-class way to do this by naming features after the
corresponding language standard.  Record them as always available in the
corresponding standard level so that requesting them always ensures that
standard (or higher) is used.

Simplify and de-duplicate per-compiler feature recording macros and
convert to a centralized per-language macro.

We have no feature tests for versions of VS older than 2010, so do
not even call `record_compiler_features` for such versions.  This
is consistent with other compilers where we call this macro only
for versions for which we have recorded features.

Refactoring in commit v3.6.0-rc1~72^2 (HDF5: Rework component searching
to correctly find HL for all bindings, 2016-05-12) changed the default
behavior from finding only the C bindings to finding everything for the
enabled languages.  Restore the original behavior for compatibility and
because many projects need only the C bindings.

Closes: #16397

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

1c52e651 Help: Update example Qt 5 find_package call to add missing component
4c802a32 Help: Update example Qt 5 find_package call to use COMPONENTS

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

13bc31aa Help: Update example Qt 5 find_package call to add missing component

Brad King authored 8 years ago and Kitware Robot committed 8 years ago

4ab3b0c4 CPackRPM: Fix incorrect variable name in documentation
e6460e7d CPackDeb: Fix incorrect variable name in documentation

Thiago M. de C. Marques authored 8 years ago and Brad King committed 8 years ago

Running CMake on it caused the following error:

    error: Target "publisher" links to target "Qt5::DBus" but the target
    was not found.  Perhaps a find_package() call is missing for an
    IMPORTED target, or an ALIAS target is missing?

Add the missing DBus component.

Thiago M. de C. Marques authored 8 years ago and Brad King committed 8 years ago

Running CMake on it caused the following error:

    error: Target "publisher" links to target "Qt5::DBus" but the target
    was not found.  Perhaps a find_package() call is missing for an
    IMPORTED target, or an ALIAS target is missing?

Add the missing DBus component.