El 07/01/2026 a las 15:56, Peter Dimov via Boost escribió:
As discussed last time, Andrey Semashev and I moved boost/static_assert.hpp from StaticAssert to Config in order to reduce nearly everyone's dependencies by one (there's no point pulling an entire repository for just one header file.)
However, this presents some issues going forward.
If I change depinst.py to properly "know" that boost/static_assert.hpp is now in Config, a lot of things break. That's because many libraries list StaticAssert as a dependency in their build.jam and CMakeLists.txt files, and since it's no longer used, depinst doesn't install it and there are errors.
What is the error? I mean those libraries that depend on StaticAssert, if the StaticAssert module no longer contains the <boost/static_assert.hpp> header (say StaticAssert is an empty module now after all include/* headers are moved to Config), why do they fail? They should find <boost/static_assert.hpp> because everyone depending on StaticAssert depends con Config... I know I'm missing something... Best, Ion