Boost 1.72

[Nicky Perian]

How are version numbers handled?

I completed a linux build and the build completed but, at autobuild package -A64 version 1.57 was assigned. The commits show 1.72 as a vendor merge. version.hpp :

#define BOOST_VERSION 105700

//
//  BOOST_LIB_VERSION must be defined to be the same as BOOST_VERSION
//  but as a *string* in the form "x_y[_z]" where x is the major version
//  number, y is the minor version number, and z is the patch level if not 0.
//  This is used by <config/auto_link.hpp> to select which library version to link to.

#define BOOST_LIB_VERSION "1_57"

Was this an oversight? Am I using 1.72?

 

[Henri Beauchamp]

boost v1.57 is still the version in use by LL's release viewer (see
the autobuild.xml file in its sources). v1.72 is the version used by
viewer-vs2017 which uses boost::fiber in place of LL's patched
boost::dcoro.

I am using boost v1.73 (and boost::fiber) for the Cool VL Viewer,
excepted for 32 bits Linux (which still uses boost v1.59 and
boost::dcoro), because sadly boost:fiber instantly crashes 32 bits
Linux builds... :-/

You can find the build script and patch I use to build boost for my
viewer here: http://sldev.free.fr/libraries/sources/

Henri.

[slacker]

You have a build copy of this in mercurial if you did not convert all your p3 p64 builds like LL did  you can find copies of all your builds I did for you I converted to git.

here. https://bitbucket.org/Drakeo/