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

Subject: Re: [Boost-users] Using Boost 1.66 with VS2017
From: Tim Burgess (tim_at_[hidden])
Date: 2018-02-01 13:11:22

John,

No problem - I'm doing exactly that and I'll ignore the warnings (I don't like suppressing such things) - what I said about increased understanding still applies, so thanks again.

Best wishes.

Tim Burgess

-----Original Message-----
From: Boost-users [mailto:boost-users-bounces_at_[hidden]] On Behalf Of John Maddock via Boost-users
Sent: 01 February 2018 13:09
To: Tim Burgess via Boost-users <boost-users_at_[hidden]>
Cc: John Maddock <jz.maddock_at_[hidden]>
Subject: Re: [Boost-users] Using Boost 1.66 with VS2017

On 01/02/2018 13:01, Tim Burgess via Boost-users wrote:
> Actually, there's a knock-on effect of downloading and copying over 
> the files, as suggested - the linker now looks for libs numbered 167, 
> which fails as my libs are 166. I tried rebuilding the libs with the 
> updated configuration in place, but still get 166-numbered files. I 
> could obviously do a global rename to get around this, but thought I'd 
> post here as a heads-up.

Oops, sorry for the bad steer.  You probably need to revert boost/version.hpp back to the 1.66 version.

>
> Best wishes.
>
> Tim Burgess
>
> -----Original Message-----
> From: Boost-users [mailto:boost-users-bounces_at_[hidden]] On 
> Behalf Of Paul A. Bristow via Boost-users
> Sent: 01 February 2018 12:37
> To: boost-users_at_[hidden]
> Cc: Paul A. Bristow <pbristow_at_[hidden]>
> Subject: Re: [Boost-users] Using Boost 1.66 with VS2017
>
>
>
>> -----Original Message-----
>> From: Boost-users [mailto:boost-users-bounces_at_[hidden]] On 
>> Behalf Of John Maddock via Boost-users
>> Sent: 01 February 2018 10:51
>> To: Paul A. Bristow via Boost-users
>> Cc: John Maddock
>> Subject: Re: [Boost-users] Using Boost 1.66 with VS2017
>>
>>
>>
>> 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/.
> Ok - it's a feature ;-)
>
> But given the rate of Visual Studio updates (roughly every Msec ;-) 
> roughly the same as time for the Boost release process to complete), 
> so the odds are that Boost will never catch up Visual Studio!).
>
> So I'm not entirely convinced that this will prove terribly helpful.
>
> It might be intuitive to say
>
>    Info: Your compiler version is newer than Boost.Config.
>
> Would a shorter message and a link to a fuller explanation like
>
>    Info: Boost.Config is older than your compiler version.
>    (See also http://boost.org/link_about_this_message.)
>
> be less clutter and not cause user 'alarm'?
>
> Paul
>
> ---
> Paul A. Bristow
> Prizet Farmhouse
> Kendal UK LA8 8AB
> [phone]
>
>
>
>
>
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> https://lists.boost.org/mailman/listinfo.cgi/boost-users
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> https://lists.boost.org/mailman/listinfo.cgi/boost-users
>

---
This email has been checked for viruses by AVG.
http://www.avg.com
_______________________________________________
Boost-users mailing list
Boost-users_at_[hidden]
https://lists.boost.org/mailman/listinfo.cgi/boost-users