On Thu, Mar 9, 2017 at 2:48 AM, Dominique Devienne via Boost < boost@lists.boost.org> wrote:

On Thu, Mar 9, 2017 at 4:25 AM, Rene Rivera via Boost < boost@lists.boost.org

...

wrote:

...

The master branch is now closed for all changes except by permission for the Beta release.

Now VS2017 *is* officially released.

Is 1.64.0 going to ship w/o built-in support for it? (given the other recent thread)

It's not out of the question yet to support it on this release. After the beta there will be some time to push fixes. And I'm working to verify the build support. Which is slowed at the moment from having to install VS through slow hotel wifi. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2017-03-09 20:57 GMT+01:00 Rene Rivera via Boost :

On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera wrote:

...

The master branch is now closed for all changes except by permission for the Beta release.

boost.fiber requires a fix for the unit-tests (Windows) - do I get permission to merge the fix to master

On Thu, Mar 9, 2017 at 2:57 PM, Rene Rivera via Boost

wrote:

On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera wrote:

...

The master branch is now closed for all changes except by permission for the Beta release.

Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: < https://dl.bintray.com/boostorg/master/>. Note that the Bintray packages also have signature files (*.asc) which can be checked with the general Bintray key at < https://bintray.com/user/downloadSubjectPublicKey?username=bintray>. And there are also sha256 hashes for the archives in machine readable JSON files.

A build using VC++ 14.0 on a Win 10 machine looks good. ...updated 1122 targets... The Boost C++ Libraries were successfully built! --Beman

On Thu, Mar 9, 2017 at 8:57 PM, Rene Rivera via Boost wrote:

On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera wrote:

...

The master branch is now closed for all changes except by permission for the Beta release.

Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: <

VS2017 / W7

.\bootstrap.bat

<OK>

./b2

...patience... ...found 11087 targets... ...updating 718 targets... compile-c-c++ bin.v2\libs\program_options\build\msvc\release\link-static\threading-multi\cmdline.obj 'cl' is not recognized as an internal or external command, operable program or batch file. -- Olaf

in order to fix the link issues in boost.fiber - I need permission to merge to master

On Sat, Mar 11, 2017 at 9:20 AM, Olaf van der Spek wrote:

On Thu, Mar 9, 2017 at 8:57 PM, Rene Rivera via Boost wrote:

...

On Wed, Mar 8, 2017 at 10:25 PM, Rene Rivera wrote:

...

The master branch is now closed for all changes except by permission for the Beta release.

Also it would be appreciated if people start testing the master snapshots for issues. You can download them directly from Bintray at: <

VS2017 / W7

...

.\bootstrap.bat

<OK>

...

./b2

...patience... ...found 11087 targets... ...updating 718 targets... compile-c-c++ bin.v2\libs\program_options\build\msvc\release\link- static\threading-multi\cmdline.obj 'cl' is not recognized as an internal or external command, operable program or batch file.

We know.. Hopefully I can address it before we put the beta out. But I'm not sure I will have time tomorrow to put in the b2 PR that deals with vs2017. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

On Sun, Mar 12, 2017 at 6:22 AM, Jürgen Hunold via Boost < boost@lists.boost.org> wrote:

Hi Rene,

Am Samstag, 11. März 2017, 17:43:53 CET schrieb Rene Rivera via Boost:

...

We know.. Hopefully I can address it before we put the beta out. But I'm not sure I will have time tomorrow to put in the b2 PR that deals with vs2017.

If you approve the current patch, I can merge the PR to develop and then master. As far as I can see, the last patch from https://github.com/boostorg/ build/issues/157 ( b2260a9 ) works fine. I've tested it with 2017 Enterprise with both Boost develop branch and my own software.

Why not do the merge to develop right way, then post a mention to this thread so others can start testing on develop. I'd rather wait for Rene to give the OK for the merge to master. I've got a P/R in for boost.config to update the MSVC 2017 version numbers for RTW. Thanks, --Beman

On Mon, Mar 13, 2017 at 4:06 PM, Tom Kent wrote:

On Sun, Mar 12, 2017 at 5:22 AM, Jürgen Hunold via Boost < boost@lists.boost.org> wrote:

...

Hi Rene,

Am Samstag, 11. März 2017, 17:43:53 CET schrieb Rene Rivera via Boost:

...

We know.. Hopefully I can address it before we put the beta out. But I'm not sure I will have time tomorrow to put in the b2 PR that deals with vs2017.

If you approve the current patch, I can merge the PR to develop and then master. As far as I can see, the last patch from https://github.com/boostorg/ build/issues/157 https://github.com/boostorg/build/issues/157 ( b2260a9 ) works fine. I've tested it with 2017 Enterprise with both Boost develop branch and my own software.

Looks like the patch went in, I just setup a temporary Azure VM running VS2017 to give library developers some feedback before the beta goes out this week. There are two runners: teeks99-07-n (develop) and teeks99-07-o (master). It looks like it is running a run about every 4 hours. I've also added that config to my normal runners, so they will start showing up there soon, but only every few days.

Hopefully I'll get a chance to build a snapshot tonight and see how that goes. Is there any schedule for when we will start with RCs for the beta?

I tried building the latest snapshot from bintray, but it doesn't find any compiler when running `bootstrap.bat`. However running `boootstrap.bat vc14.0` works, so something in bootstrap's lookup logic? Tom