The topic itself is already few months old, namely the fact that Boost.Filesystem <br>library breaks on Mingw in DLL builds. As I see from regression tests, this issue <br>hasn't been fixed yet. The reason I'm bringing this up again is that while originally 
<br>it was concluded that static builds should be used on Mingw instead of DLL builds, <br>it is becoming an increasing problem for me, since default_name_check doesn't work <br>across DLL boundaries when B.FS is linked statically to one of the DLL's, which
<br>results unexpected exceptions being thrown all over my codebase unless I explicitly<br>construct paths using native name-checker, but tracking all those places is a constant<br>headache.<br><br>Is there any plans on addressing this issue, or are there any additional workarounds 
<br>to have default_name_check functioanlity working across DLL boundaries when <br>Boost.Filesystem is linked statically? My experience has been that mixing dynamic <br>and static libraries is a really bad idea...<br><br>
Alo Sarv<br><br>