* accept double digits in Python3_VERSION_MINOR
* if someone is using e.g.:
find_package(Python3 REQUIRED)
find_package(Boost REQUIRED python${Python3_VERSION_MAJOR}${Python3_VERSION_MINOR})
with python-3.10 then it currently fails with:
-- Found PythonLibs: /usr/lib/libpython3.10.so (found version "3.10.0")
-- Found Python3: -native/usr/bin/python3-native/python3 (found version "3.10.0") found components: Interpreter
CMake Error at /usr/lib/cmake/Boost-1.77.0/BoostConfig.cmake:141 (find_package):
Could not find a package configuration file provided by "boost_python310"
(requested version 1.77.0) with any of the following names:
boost_python310Config.cmake
boost_python310-config.cmake
Add the installation prefix of "boost_python310" to CMAKE_PREFIX_PATH or
set "boost_python310_DIR" to a directory containing one of the above files.
If "boost_python310" provides a separate development package or SDK, be
sure it has been installed.
Call Stack (most recent call first):
/usr/lib/cmake/Boost-1.77.0/BoostConfig.cmake:258 (boost_find_component)
/usr/share/cmake-3.21/Modules/FindBoost.cmake:594 (find_package)
CMakeLists.txt:18 (find_package)
Signed-off-by: Martin Jansa <martin.jansa@lge.com>
* This new meta-component instructs BoostConfig.cmake to parse its
parent-directory for installed Boost components and will provide
imported targets for them as if they were listed as components in the
call to `find_package`.
* If this new component is used it has to be the only component
provided to the `find_package` call.
* If another component is provided together with the "ALL" component a
non-fatal error will be triggered (with a hint for how to fix that
error) but the script will continue looking for all components,
ignoring that additional component.
However, as typical for non-fatal errors CMake configuration will
still fail in the end.
* If BoostConfig.cmake was triggered by FindBoost.cmake with that
meta-component it will continue to work as if `find_package` was
called in config mode, but FindBoost.cmake might print a warning if
either `Boost_DEBUG` or `Boost_VERBOSE` was set.
