Re: [Boost-users] Using Boost 1.66 with VS2017

Subject: Re: [Boost-users] Using Boost 1.66 with VS2017
From: John Maddock (jz.maddock_at_[hidden])
Date: 2018-02-01 10:50:49

On 01/02/2018 10:13, Paul A. Bristow via Boost-users wrote:
>
> *From:*Boost-users [mailto:boost-users-bounces_at_[hidden]] *On 
> Behalf Of *Tim Burgess via Boost-users
> *Sent:* 31 January 2018 17:39
> *To:* 'boost-users list'
> *Cc:* Tim Burgess
> *Subject:* [Boost-users] Using Boost 1.66 with VS2017
>
> Hi,
>
> I’m getting the following message during compilation of my application:
>
> 1>Info: Boost.Config is older than your compiler version - probably 
> nothing bad will happen - but you may wish to look for an update Boost 
> version.  Define BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE to suppress 
> this message.
>
> I don’t want to suppress the message, but would appreciate any mods I 
> need to do to actually stop its cause.
>
> Many thanks in advance for any suggestions.
>
> As I understand it, ‘it’s a bug’ and even if you use the latest 
> version of Boost (or even the unreleased develop branch) you will 
> still get the message.
>

Not a bug - that's the way it's supposed to work.  It's a gentle warning 
that the Boost release you're using hasn't been tested with that msvc 
release.

VS2017 update 5 came out at about the same time as 1.66 so we hadn't had 
a chance to adjust Boost.Config for the new features in that release, 
neither did we have a regression test runner for that compiler at that 
time.   So you can either:

* Ignore it and wait for 1.67: some compiler features which could have 
been enabled will still be disabled (as per the previous msvc release).
* Define the macro indicated to shut it up.
* Download the current Boost.Config master from 
https://github.com/boostorg/config/archive/master.zip and extract the 
contents of /include/boost/ over the top of your boost-root/boost/.

HTH, John.

---
This email has been checked for viruses by AVG.
http://www.avg.com