-----Original Message----- From: Boost On Behalf Of Andrey Semashev via Boost Sent: 24 September 2020 09:30 To: boost@lists.boost.org Cc: Andrey Semashev Subject: Re: [boost] [nowide] cxx11_moveable_fstreams target

On 9/24/20 11:19 AM, Alexander Grund via Boost wrote:

...

Is there some common practice where to put such configure checks that are required to build the library?

I'm putting configure/build time checks in the config directory at the top level of the library.

But I don't think there is an official guideline wrt. this.

I think there should be. And not just in JSON metadata. But it is a big job for some libraries, duplicating what is in jamfiles. Should we start a new thread to discuss specific proposals? Paul

-----Original Message----- From: Boost On Behalf Of Alexander Grund via Boost Sent: 24 September 2020 11:59 To: boost@lists.boost.org Cc: Alexander Grund Subject: [boost] Configure check guidelines

...

...

On 9/24/20 11:19 AM, Alexander Grund via Boost wrote:

...

Is there some common practice where to put such configure checks that are required to build the library? I'm putting configure/build time checks in the config directory at the top level of the library. But I don't think there is an official guideline wrt. this. I think there should be. And not just in JSON metadata. But it is a big job for some libraries, duplicating what is in jamfiles.

Starting a new thread. TLDR: Where should (source)files go that are required during the "configure" step of a regular build?

Not sure what is meant by JSON metadata as I don't see how that is related. Can you elaborate?

This was Edward Diener's original suggestion that the Boost metadata currently giving name, author etc could include the C++ standard level applicable. It is the data for this list https://www.boost.org/doc/libs/ The discussion is here, for the record and new people joining this thread http://boost.2283326.n4.nabble.com/Proposal-for-adding-C-level-to-the-meta-l... HTH Paul

Configure checks that require source files typically do not check for C++ version or features. For that there are already pre-defined rules in Boost.Config. I had the need for one: Moveable streams which are C++11 but not implemented by all stdlibs -.-

To me, the existing practice (using config top level directory) seems fine. We might as well document it. +1 I see 7 other libs doing that, so making it official seems good

On 24/09/2020 11:58, Alexander Grund via Boost wrote:

...

...

...

Is there some common practice where to put such configure checks that are required to build the library? I'm putting configure/build time checks in the config directory at

On 9/24/20 11:19 AM, Alexander Grund via Boost wrote: the top level of the library. But I don't think there is an official guideline wrt. this. I think there should be.  And not just in JSON metadata.  But it is a big job for some libraries, duplicating what is in jamfiles.

Starting a new thread. TLDR: Where should (source)files go that are required during the "configure" step of a regular build?

I've always put them under /config. But there's nothing official about that.  Placing them under /build would also be just fine I would think. John.

Not sure what is meant by JSON metadata as I don't see how that is related. Can you elaborate?

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

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