On 7 Jan 2026 20:30, Alexander Grund via Boost wrote:
Am 07.01.26 um 18:19 schrieb Andrey Semashev via Boost:
On 7 Jan 2026 20:04, Alexander Grund via Boost wrote:
Am 07.01.26 um 17:56 schrieb Andrey Semashev via Boost:
Please, postpone the changes to depinst until we update all the libraries to avoid the dependency on StaticAssert. Then we update depinst and remove the StaticAssert submodule. Just to be clear: "remove the submodule" does not mean deleting the library but only not installing it with depinst? No, the submodule will stop being downloaded after depinst is updated (and CI configs, if they happen to have the StaticAssert dependency hardcoded now).
"Remove" means remove, i.e. https://github.com/boostorg/static_assert will no longer exist. And which of those 2 things are you suggesting? The latter?
Both. But not necessarily at the same time (i.e. in the same Boost release).
Because this will surely break many users that rely on e.g. the `Boost::static_assert` CMake target
Users will have to update their dependencies to remove `Boost::static_assert`.
So at least that should be included in Boost.Config as an alias for Boost::headers/config including the generated (by b2) config files
We could do that, in principle, although I would prefer to avoid piling dummy targets with no clear plan to remove them. I'd rather declare the StaticAssert submodule deprecated in release notes of Boost N and then remove it, along with targets, in e.g. N+3.
I'm not sure if it is possible to deprecate CMake targets in a way that causes proper warnings/errors, which would be a way forward.
Yes, if there is a way to generate warnings, that would be great. I'm not aware of one, though.