Subject: Re: [boost] Best Practices for Surviving the Boost Test Gauntlet?
From: Gavin Lambert (gavinl_at_[hidden])
Date: 2017-08-10 22:56:12
On 10/08/2017 13:57, Edward Diener wrote:
> This is almost exclusively for libraries which have been around for a
> long time. Boost fully accepts the fact that your library may need a
> particular level of c++ compliance. The important thing is to document
> the level of c++ compliance needed by your library. Once you have done
> that then it is the end-user's problem if they are using a compiler that
> does not meet the level of c++ that your library needs if they wish to
> use your library.
While that's true, it's also polite to have your Jamfile configured to
skip compiling on the unsupported platforms, so that the user doesn't
have to explicitly opt out with --without-xxx.
Although it's not as big a deal for header-only libraries, since the
default build doesn't build the tests anyway, IIRC.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk