Subject: Re: [boost] Modularizing explicit-failures-markup.xml
From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2017-10-01 17:55:10
On Sun, Oct 1, 2017 at 10:10 AM, Daniel James via Boost
> I'm looking into implementing a mechanism for updating
> explicit-failures-markup.xml without updating the super project.
If I could humbly request a feature, I would like a way to indicate in
the explicit-failures-markup.xml that my library should not attempt to
be compiled on a particular configuration. For example, Beast requires
C++11 so it would be nice if 1. No time was wasted attempting to build
beast on pre-C++11 environments, and 2. the column in the test matrix
is colored or shaded to indicate that it is known to be an unsupported
For example, Beast cannot compile on msvc-12 or earlier (because no
C++11), yet it shows errors in the matrix here:
I would like those columns to indicate that it is not a supported platform.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk