On Mon, Nov 21, 2016 at 9:41 AM, Olaf van der Spek
On Mon, Nov 21, 2016 at 1:49 PM, Jürgen Hunold
wrote: Hi Olaf,
Am Montag, 21. November 2016, 13:19:57 CET schrieb Olaf van der Spek:
On Mon, Nov 21, 2016 at 10:50 AM, Jürgen Hunold
wrote: Yes, until MS changed the install path's of Visual Studio with Preview 5. And again with the RC. So we need to adopt Boost.Build again in the hope the current directory layout is kept for the final.
The path issue is a minor issue.
"path" includes registry entries. And both are evaluated. And yes, that is a major issue, as you see below.
I think 1.62 used to be buildable with the preview..
That is what I said. I think I merged the relevant PR and to master. Thus Preview 4 works, Preview 5 changed paths and registry entries, RC again.
So bootstraps can't automatically find cl.. that's minor IMO.
But if cl is in the path, there's another issue..
Who's the resident Boost Build expert? IMO it'd be very nice to have VS2017 working.
Too late for the release, I suspect. And it is still a preview compiler with a lot of issues to be fixed in develop anyway.
Sure, but I think VS gets released before Boost 1.64.
+1 VS2017 is a major step forward for VC++ users, so the faster Boost Build works OK with it the better. But that said, we need to get on with 1.63. --Beman