| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
On platforms where our default Boost static library prefix is incorrect,
make it possible for users to set it explicitly to work around the problem
until FindBoost can be updated.
Fixes: #20372
|
|
|
|
| |
Also add a comment explaining its purpose.
|
|
|
|
|
|
|
| |
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
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
907d3ed824 FindBoost: Tolerate future Boost INTERFACE libraries
2d357b7a68 FindBoost: Clarify role of legacy variables in warning message
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3780
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since commit 0dd6772a89 (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 0dd6772a89 (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
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
7828577065 FindBoost: Add support for Boost 1.71
cf29fa18c8 FindBoost: Unwrap compatibility INTERFACE targets for legacy variables
d7df3cd73f FindBoost: Remove incorrect 1.70 timer dependency
8ff43de1a5 FindBoost: Simplify conditional block for last known version
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Dennis Klein <d.klein@gsi.de>
Merge-request: !3763
|
| |
| |
| |
| |
| |
| |
| | |
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 0dd6772a89 (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.
|
|/ |
|
|
|
|
|
| |
This allows future BoostConfig to NOT define those and users relying on
them use the newer FindBoost of newer CMake versions
|
|
|
|
| |
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
|
|\
| |
| |
| |
| |
| |
| | |
b915a42585 FindBoost: Add compiler features for Boost Contract library
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3368
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
This aligns module mode behaviour with config mode.
|
| | |
|
| |
| |
| |
| | |
Fixes: #19186
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
f06bf0fa57 FindBoost: Fix compiler features for `fiber` and `context`
684338aff6 FindBoost: Record compiler features for Boost 1.67 and above
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3266
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| |\
| | |
| | |
| | | |
Merge-request: !3237
|
| | |
| | |
| | |
| | | |
Generalize the logic to express compatibility among 14.x versions.
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
0b54f72e94 FindBoost: Fix detection with version suffixes on Gentoo
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3237
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
The Gentoo case added by commit 1673923c30 (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.
|
| | |
|
| |
| |
| |
| |
| | |
When compiling with `clang-cl` we can use either the MSVC- or
Clang-built boost libraries.
|
|/
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| |
| |
| | |
0369362132 FindBoost: Restore finding without CXX language enabled
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2663
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |\
| | |
| | |
| | | |
Merge-request: !2601
|
| | | |
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
5045cd82d0 FindBoost: Additional fixes for 1.69
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2601
|
| | | |
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
b71667a395 FindBoost: Improve compiler prefix detection for GCC 5+ and clang 4+
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2579
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
bd831ed094 FindBoost: Add system thread library to Boost_LIBRARIES
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2570
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Add the system thread library to Boost_LIBRARIES when the boost thread
component has been found.
The Boost::thread imported target already pulls in Threads::Threads.
This changes does the same for projects using the Boost_LIBRARIES variable
instead.
|