Ion Gaztañaga wrote:
El 07/01/2026 a las 16:23, Peter Dimov via Boost escribió:
Ion Gaztañaga wrote:
What is the error?
error: Unable to find file or target named error: '/boost/static_assert//boost_static_assert' error: referred to from project at error: '/__w/boostdep/boost-root/libs/detail' error: could not resolve project reference '/boost/static_assert'
https://github.com/boostorg/boostdep/actions/runs/20784697352/job/5969085263...
Is that because b2 searches for some info under folder libs/static_assert (say, build.jam or similar)?
I mean, where does the build system expect to find "target name" "/boost/static_assert//boost_static_assert"?
This target name is declared in libs/static_assert/build.jam, exactly like for any other library. The way this works (before the change) is as follows. depinst sees boost/static_assert.hpp. Since the file is called "static_assert.hpp", it assumes it belongs to the library "static_assert", and does "git submodule update static_assert". This downloads the static_assert repo in libs/static_assert. The build.jam there declares the target above. Why this doesn't work after the change: depinst sees that "boost/static_assert.hpp" is an exception and doesn't reside in the static_assert submodule but in the config submodule. It doesn't do "git submodule update static_assert", and libs/static_assert remains an empty subdirectory. Being empty, it doesn't contain build.jam, which consequently doesn't declare the target above. libs/detail/build.jam breaks because it can't find the target. The end.