Subject: Re: [boost] Status of Visual Studio 2017 support
From: Olaf van der Spek (ml_at_[hidden])
Date: 2017-02-22 08:01:57
On Tue, Feb 21, 2017 at 4:23 PM, Rene Rivera via Boost
<boost_at_[hidden]> wrote:
> Thirst; But this all detracts from the key point. The current situation
> with using VS2017 to bootstrap a C++ compilation is problematic. And it's
> something the VS team has known for months. Given the comments by various
> other teams dealing with the exact same situation. As evidenced by comments
> in the blog posts in the VS announcements of said structural changes. And
> so far the solutions suggested by the VS team amount to everyone else other
> than VS duplicating the work in every project that has the issue in rather
> bad kludged code.
Does using the "Developer Command Prompt for Visual Studio" start menu
entry avoid this roadblock?
-- Olaf