Boost logo

Boost Users :

Subject: Re: [Boost-users] LLVM bitcode for Boost libraries?
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2018-12-04 10:17:28



From: Boost-users [mailto:boost-users-bounces_at_[hidden]] On Behalf Of degski via Boost-users
Sent: 30 November 2018 20:40
To: boost-users_at_[hidden]
Cc: degski
Subject: Re: [Boost-users] LLVM bitcode for Boost libraries?


On Fri, 30 Nov 2018 at 16:09, Osman Zakir via Boost-users <boost-users_at_[hidden]> wrote:

So you mean I should use Clang-C2/Clang with Microsoft CodeGen, aka the clang-cl compiler? Either way, how do I change the compiler toolchain when building Boost?


No, that's dead for a [quite] while now, just get and install Clang/LLVM from


AFAIK, the final Boost-1.69 release [or current dev branch] will allow for building with clang-cl **and lld-link** [Thanks to Peter Dimov]. You'll need to have a project-jam file something like this:


import option ;
using clang-win : : "C:\\Program Files\\LLVM\\bin\\clang-cl.exe" -fuse-ld=lld :


But you'll have to adjust that to your needs.


Before I bash my head against this configuration again, please can you confirm that this does this work for you to build the Boost libraries **on Windows** so that one can use the Boost.Test library (not header-only)?


Am I right on thinking that


All the / items are to allow compilation of MSVC stuff.


Is it essential to use <cxxflags>"/EHsc" ? when


test suite using Boost. emits a warning that EHa should be enabled:

warning C4535: calling _set_se_translator() requires /EHa


All the –Wno- items are to deal with a blizzard of warnings from MSVC stuff?


    <cxxflags>-D_CRT_SECURE_NO_WARNINGS is need to avoid C runtime warnings.


And all the other –D items are only needed if you want to use more than empty project console applications?







Boost-users list run by williamkempf at, kalb at, bjorn.karlsson at, gregod at, wekempf at