Re: [boost] select_stdlib_config.hpp including <version> vs <VERSION> on OS X

Hello, Thanks for the replies. I had not found the issue in my search as I knew I could not be the first to encounter this issue. After reading the issue and the links I agree that it is not a boost problem. But a new paradigm that projects are going to need to adapt to going forward. With the <version> now being a C++20 file there is going to be lots of file renaming across many projects in the near future as I did a find file for VERSION across several software projects I use locally and it is quite prevalent. Glad I only actively develop on a few projects. Thanks and Cheers, Allen Allen Sanderson SCI Institute University of Utah

On Apr 9, 2021, at 4:09 AM, John Maddock via Boost wrote:

...

The issue is that many projects (gnuplot, builtbot, and others) have a VERSION file in their top level src directory. On a traditional Linux system the case sensitivity would make sure the right file is included. However, many/most OS X file systems are case insensitive. As such, the project's VERSION file gets included instead. And does not compile.

I have no solution to the issue other than I renamed our project’s VERSION file for the time being. However, I wanted to raise the issue as I noticed it when moving to 1.75 and backtracked out that it was a recent changed starting with boost 1.73

We have a recurring issue filed on this here: https://github.com/boostorg/config/issues/345

So while I agree it's annoying, and I feel your pain, the fact is that <version> is a std lib header, and a very useful one (for us at least), so while you might have hit this issue here first, it's likely to become more and more common over time.

Best, John.

-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost