4 Jun
2021
4 Jun
'21
2:22 p.m.
Andrey Semashev wrote:
My stance on this is that Boost.Filesystem must be built on a system with kernel headers matching or older than the systems that will run the binary. This matches the same requirements for Windows. I don't support configs with headers newer than runtime kernel.
I don't think this is a realistic requirement to put on users. Is it possible to handle the runtime failure and fall back on the no-statx code path?