14 Jan
2019
14 Jan
'19
8:48 p.m.
Rene Rivera wrote:
On Mon, Jan 14, 2019 at 2:35 PM Niall Douglas via Boost < boost@lists.boost.org> wrote:
I guess ideally speaking Boost.Config gains a new test testing for this specific compiler parsing bug. But it seems a bit much to ask for this just for Outcome.
One option is to use the Predef checks https://www.boost.org/doc/libs/release/doc/html/predef/check_utilities.html#.... Another option is to implement a check program of your own.
Would it be possible to make `<toolset>gcc-5:<build>no` match `toolset=gcc`, major version 5, any minor version? At present, it requires an exact version match, which isn't very convenient. Similarly, <toolset>gcc-4.6 should match f.ex. gcc-4.6.2.