Page 1 of 1

Latest version of BOOST.

Posted: 2019-12-19 01:40
by SorenR
Anyone got an idea why BOOST 1.70.0 is preferred over the latest version?

hMailServer 5.6.8 does actually compile (x86 32bit) without errors when using BOOST 1.72.0. I have not run it more than 5 minutes yet...

I have Windows 10 Home x64 1909 (latest and greatest ;-) )
I use Microsoft Visual Studio Community 2013 Update 5 and like the Express versions the Windows Driver Kit 7.1 must be installed.

Using the Community edition over Express versions enables the use of extensions, f.ex. code formatting scripts like "Format All Files" ...
https://marketplace.visualstudio.com/it ... atAllFiles

Building the bootstrap in BOOST 1.72.0 did present some issues however.
Building Boost.Build engine
The system cannot find the batch label specified - Config_VC12
Never found the reason why it would say that but I found a workaround ;-)

REM'ing out the 3 last lines solved the problem. No idea why and it was a spur of the moment that triggered REM'ing all unused options.

File: C:\dev\lib\boost_1_72_0\tools\build\src\engine\config_toolset.bat

Code: Select all

:Start
REM Setup the toolset command and options.
if "_%B2_TOOLSET%_" == "_msvc_" call :Config_MSVC
if "_%B2_TOOLSET%_" == "_vc11_" call :Config_VC11
if "_%B2_TOOLSET%_" == "_vc12_" call :Config_VC12
if "_%B2_TOOLSET%_" == "_vc14_" call :Config_VC14
if "_%B2_TOOLSET%_" == "_vc141_" call :Config_VC141
if "_%B2_TOOLSET%_" == "_vc142_" call :Config_VC142
if "_%B2_TOOLSET%_" == "_borland_" call :Config_BORLAND
if "_%B2_TOOLSET%_" == "_como_" call :Config_COMO
if "_%B2_TOOLSET%_" == "_gcc_" call :Config_GCC
REM if "_%B2_TOOLSET%_" == "_gcc-nocygwin_" call :Config_GCC_NOCYGWIN
REM if "_%B2_TOOLSET%_" == "_intel-win32_" call :Config_INTEL_WIN32
REM if "_%B2_TOOLSET%_" == "_mingw_" call :Config_MINGW
exit /b %errorlevel%
Also bjam.exe is not created anymore.

Code: Select all

b2.exe --toolset=msvc-12.0 --build-type=complete address-model=32 --build-dir=out32 -j 4

Re: Latest version of BOOST.

Posted: 2019-12-19 02:16
by SorenR
SorenR wrote:
2019-12-19 01:40
Building the bootstrap in BOOST 1.72.0 did present some issues however.
Building Boost.Build engine
The system cannot find the batch label specified - Config_VC12
Never found the reason why it would say that but I found a workaround ;-)

REM'ing out the 3 last lines solved the problem. No idea why and it was a spur of the moment that triggered REM'ing all unused options.

File: C:\dev\lib\boost_1_72_0\tools\build\src\engine\config_toolset.bat
OK figured it out... It's some sort of sick joke from Microsoft.

I use NotePad++ and it does not really care about line endings so everything looked fine ... BUT ... Changing LF's to CRLF's in a fresh copy of the file config_toolset.bat did the trick!

Re: Latest version of BOOST.

Posted: 2019-12-19 22:24
by RvdH
SorenR wrote:
2019-12-19 01:40
Anyone got an idea why BOOST 1.70.0 is preferred over the latest version?
Who says BOOST 1.70.0 is preferred over the latest version?

Maybe simply because those newer releases are released after the latest commits done by martin? (he merged some pull request since, and upgraded openssl but nothing more)
Boost 1.72.0 December 11th, 2019, Boost 1.71.0 August 19th, 2019

:mrgreen:


Any reason tho upgrade to BOOST 1.72.0? Something is not working with 1.70.0?
You can upgrade BOOST about every two months if you like, newer != better :wink:

Re: Latest version of BOOST.

Posted: 2019-12-20 07:21
by SorenR
RvdH wrote:
2019-12-19 22:24
Any reason tho upgrade to BOOST 1.72.0? Something is not working with 1.70.0?
You can upgrade BOOST about every two months if you like, newer != better :wink:
No particular reason. Just curios... I know BOOST is covering a lot of code so perhaps I should just try to isolate the used functions in case some of them gets modified/updated at some point.