On Sun, 22 Dec 2024 at 14:29, Cameron Angus via Boost
The targets are installed by the Boost.CMake infrastructure
As mentioned in the Slack discussion I'm more of a build2 user lately so my CMake knowledge is a bit out of date. It's possible there is also some Windows/Linux difference here. However, I'm sure that in CMake projects I've worked on in the past, we've always used boost without an install step. The boost CMake scripts would simply be pulled (one way or another, CMake seems to have many ways of doing things, and I guess package managers are another way of doing this) into the project, and boost targets linked against as needed. With this approach, boost components are simply built as part of the consuming project so there are none of the issues that come with prebuilt binaries.
I realise that installation is something that needs to be solved eventually, but I'd be surprised if the above approach wasn't fairly common, so if it works I think it would be the most straightforward and a good first goal to aim for.
I think we usually refer to this as the "add_subdirectory workflow". Maybe I'm worrying about the installation workflow too much. We don't maintain the CMake scripts that package managers use AFAIK, so I can't speak about them.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost