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

From: Allen Sanderson (allen_at_[hidden])
Date: 2021-04-12 17:42:19

Alex,

You are correct. For the project I am working on this issue is entirely “our” fault as in the top level CMakeLists.txt file the following was included:

INCLUDE_DIRECTORIES(${CMAKE_SOURCE_DIR})

That should have never been included (pun intended). I looked at some other projects with a VERSION file. Some are in a directory with header file files. Those will probably have some build issues going forward.

Thanks for everyone’s help and guidance.

Cheers,

Allen 

> On Apr 9, 2021, at 11:31 AM, Alexander Grund via Boost <boost_at_[hidden]> wrote:
> 
> Am 09.04.21 um 19:13 schrieb Allen Sanderson via Boost:
>> 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.
> FWIW: No renaming is needed, if the file is not added to the include path. And IMO only the minimal required amount of stuff should be there, so having that file in the include path is already a bad sign. It also means that less projects may be affected as you fear :)
> 
> 
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost