| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
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.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Boost 1.66 and above built with `--layout=versioned` add an architecture
tag to the library file names. We already try to compute this tag
automatically when `CMAKE_CXX_COMPILER_ARCHITECTURE_ID` is available,
but that is currently not computed everywhere. Add an explicit
`Boost_ARCHITECTURE` option that a user can set to specify the
architecture tag.
Issue: #17701
|
| |\
| | |
| | |
| | | |
Merge-request: !2541
|
| |\ \
| | | |
| | | |
| | | | |
Merge-request: !2522
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
9855a80fd4 FindBoost: search default path if Boost_FIND_VERSION_EXACT
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2543
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Search paths for boost versions should be build using _boost_TEST_VERSIONS
instead of _Boost_KNOWN_VERSIONS because if Boost_FIND_VERSION_EXACT
is used _Boost_KNOWN_VERSIONS is empty and boost isn't found even in its
default installation path.
Fixes: #17986
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
c664470966 FindBoost: Output Boost_LIB_PREFIX if Boost_DEBUG=ON requested
Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Roger Leigh <rleigh@codelibre.net>
Merge-request: !2548
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
Output Boost_NAMESPACE too.
|
|\ \ \ \ \
| |/ / / /
|/| | | /
| | |_|/
| |/| |
| | | |
| | | |
| | | | |
b27cf72dea FindBoost: Add support for stacktrace components
Acked-by: Kitware Robot <kwrobot@kitware.com>
Reviewed-by: Roger Leigh <rleigh@codelibre.net>
Merge-request: !2541
|
| | |/
| |/|
| | |
| | |
| | |
| | | |
Define the headers associated to `boost_stacktrace_*`.
Fixes: #17297
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
364fb69adc FindBoost: Add support for upcoming Boost 1.69
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Mateusz Łoskot <mateusz@loskot.net>
Merge-request: !2522
|
| | |
| | |
| | |
| | | |
This makes the module usable with Boost from its current master.
|
| |/
|/| |
|
|/
|
|
|
| |
We were searching the `-mt` variant for debug libs only.
It makes sense for release libs too.
|
|
|
|
| |
Fixes: #18330
|