Orgad Shaneh authored Apr 25, 2020 and Brad King committed Apr 27, 2020

In commit 9daf79c5 (FindBoost: Add support for Boost 1.73, 2020-04-19)
we forgot to update the version comparison for the warning.

Alexander Grund authored Apr 19, 2020 and Brad King committed Apr 20, 2020

Run `Utilities/Scripts/BoostScanDeps.cmake` with the Boost 1.73.0
sources to compute dependencies.

This includes a new Boost.Nowide library.

Special case: Boost.Filesystem is an optional dependency as the include
is only required to make Boost.Filesystem use UTF-8 paths on user
request

Niall Murphy authored Jan 25, 2020 and Brad King committed Jan 27, 2020

Move creation of the "helper" targets that do not require anything to be
found to be done only after Boost is found.

Fixes: #20261

Run `Utilities/Scripts/BoostScanDeps.cmake` with the Boost 1.72.0
sources to compute dependencies.

Fixes: #20100

Since commit 0dd6772a

 (FindBoost: Add legacy variables and targets for
compatibility, 2019-06-14, v3.15.0-rc2~3^2~1) we query imported targets
provided by `BoostConfig.cmake` for their `IMPORTED_LOCATION_<cfg>`.
Querying this property is not allowed on INTERFACE libraries, so add a
condition to avoid doing so in case Boost adds one in the future.
Suggested-by: Alexander Grund <alexander.grund@tu-dresden.de>
Issue: #19656, #19402

Revise the wording of the warning added by commit 0dd6772a

 (FindBoost:
Add legacy variables and targets for compatibility, 2019-06-14,
v3.15.0-rc2~3^2~1) to refer to the old variables as "legacy" rather
than "standard".
Suggested-by: Alexander Grund <alexander.grund@tu-dresden.de>
Issue: #19402

Run `Utilities/Scripts/BoostScanDeps.cmake` with the Boost 1.71.0
sources to compute dependencies.  They are the same as Boost 1.70.

Fixes: #19658

Since commit 0dd6772a (FindBoost: Add legacy variables and targets for
compatibility, 2019-06-14, v3.15.0-rc2~3^2~1) we extract information
from imported targets provided by upstream `BoostConfig.cmake` files.
However, upstream Boost 1.71 provides some imported targets only for
compatibility.  They are just INTERFACE libraries that wrap around the
real target named by `INTERFACE_LINK_LIBRARIES`.  Unwrap this layer so
we can extract the real imported location.

Fixes: #19656

Running `Utilities/Scripts/BoostScanDeps.cmake` with the Boost 1.70.0
sources shows that the `timer` component no longer depends on `system`.
This is consistent with upstream Boost Timer commit `43eecbd071`.

A version newer than we know about will be large enough to enter the
block for the last known version so we can put the warning there.

Alexander Grund authored Jun 14, 2019 and Brad King committed Jun 18, 2019

This allows future BoostConfig to NOT define those and users relying on
them use the newer FindBoost of newer CMake versions

Alexander Grund authored Jun 11, 2019 and Brad King committed Jun 18, 2019

Is set in Boost >= 1.71 so don't overwrite it

* Deduplicate code with helper functions
* Remove double printing of _boost_TEST_VERSIONS
* Fix #19158
* Add printing of a few additional variables

CMake 3.12 introduced <package>_ROOT CMake and environment variables to
be valid hints to find_package(<package>). Defining Boost_ROOT is no
longer wrong if CMP0074 is set to NEW.

Fixes #18810

Dennis Klein authored May 03, 2019 and Brad King committed May 13, 2019

This aligns module mode behaviour with config mode.

Fixes: #19186

Alex Turbov authored Apr 26, 2019 and Brad King committed Apr 30, 2019

Remove the 1.67 upper-bound on compiler feature computation so that with
newer versions we at least get it mostly right.  Leave a comment with
notes about updating features for future versions.

Rolf Eike Beer authored Apr 15, 2019 and Brad King committed Apr 16, 2019

The Gentoo case added by commit 1673923c (FindBoost: Add support for
Boost 1.67 with Python version suffixes, 2018-03-18, v3.11.0~3^2) left
out the `.` version component separator and instead duplicated the RPM
case.  Add the missing `.` now.

Fixes: #18743

Generalize the logic to express compatibility among 14.x versions.

Generalize the logic to express compatibility among 14.x versions.

Douman authored Mar 29, 2019 and Brad King committed Apr 03, 2019

When compiling with `clang-cl` we can use either the MSVC- or
Clang-built boost libraries.

NeroBurner authored Mar 11, 2019 and Brad King committed Mar 11, 2019

The purpose of the `Boost::dynamic_linking` interface library is to
cause `BOOST_ALL_DYN_LINK` to be defined.  Do this on all platforms
instead of just Windows.

In particular, using Boost::log trivial_logger requires to set
BOOST_ALL_NO_LIB when Boost::Log is compiled as dynamic library.

Fixes: #17813

Yves Frederix authored Feb 14, 2019 and Brad King committed Feb 18, 2019

Pick up libraries of the form `boost_system-mt-x64`, which do not have
the version suffix.

Fixes: #18908

Boost master and develop branches just bumped the version.

Since commit v3.13.0~7^2 (FindBoost: Improve compiler prefix
detection for GCC 5+ and clang 4+, 2018-11-07) we run the internal
`_Boost_COMPILER_DUMPVERSION` macro on all UNIX platforms.  Teach
the macro to tolerate missing `CMAKE_CXX_COMPILER_VERSION`, which
occurs when the CXX language is not enabled.

Fixes: #18624

Mateusz Łoskot authored Nov 07, 2018 and Brad King committed Nov 09, 2018

Add recognition of compiler version and prefix for clang.
Accommodate changes to version numbering scheme for GCC 5+ and clang 4+
 - Minor number becomes patch, so excluded it from compiler prefix.
 - Improves searching for Boost 1.69+ libraries built with GCC 5+ and
   clang 4+, where library names are generated with compiler tag based on
   major version only eg. -gcc5 for GC 5.5.0 or -clang6 for clang 6.0.0
 - Follows up related changes in upcoming Boost 1.69
   https://github.com/boostorg/build/pull/349
Dump detected compiler version in Boost_DEBUG message.
Replace use of CMAKE_COMPILER_IS_GNUCXX with CMAKE_CXX_COMPILER_ID.