-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is the cmake configuration in Boost deleted when packaging ? #1818
Comments
My understanding is Conan itself supports being able to save CMake config files in Conan packages, but Conan Center doesn't believe this is a good practice. The reasoning is when the CMake config files are called they create their own graph for all of a project's transitive dependencies which may or may not match up to Conan's, which leads to problems. The example I was given is that they may include a system installed version of openssl while other dependencies from the same project are using a newer version specified by Conan. However my understanding is recent additions to Conan enable it to emulate most things the "official" CMake package config files are doing. It's possible to use |
@sflis The motivation for removing: https://github.com/conan-io/conan-center-index/wiki/FAQ#why-are-cmake-findconfig-files-and-pkg-config-files-not-packaged About the modules for Boost, there is an initial effort: #1925
This won't happen. Conan 1.26 provides a new support for modules, involving cmake_find_package generator. It should be enough for generating the correct FindBoost.cmake file (including the modules), it's just a matter of time until having that PR available. |
If needed, please continue on this issue #209. I suppose this is not specific to Boost itself and it is easier to try to centralize things. Thanks! |
Why is the cmake configuration in Boost deleted when packaging?
conan-center-index/recipes/boost/all/conanfile.py
Line 826 in ca5040f
From boost 1.70 boost provides its own cmake configuration file which depracated the BoostFindModule.cmake that cmake provides. If I chose to use cmake for package discovery by using find_package( ) together with the
cmake_paths
generator in conan it will not find the configuration file since it is removed in the conan package. Instead it will pick up the BoostFindModule.cmake.This does not follow cmake best practices. I would like to propose to remove that line and ship boost with it's cmake configuration.
The text was updated successfully, but these errors were encountered: