On Tue, Mar 21, 2017 at 12:36 PM, Tom Kent
It looks like the boostorg/boost:master commit this snapshot was based off doesn't have the latest boostorg/config:master submodule commit. I think updating this is a manual process at this point in the release cycle? (Thus the autolink file is still looking for vc150).
Grr.. Forgot to do that for config. I did it for build though :-) It's done now.. Just need to wait again for the new archives.
As an aside, I had a difficult time figuring out what the snapshot I downloaded referred to. I was able to use the boost_1_64_0_snapshot.tar.bz2.json file to determine that I had the correct boost_1_64_0_snapshot.tar.bz2, but bintray doesn't make it super clear what git commit this snapshot download refers to.
Would it be possible to add a file to snapshots/releases that contains the git commit hash?
Can't promise I'll do it right this second... But I'll add the commit hash to the json data for the archives. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail