Re: [Boost-build] Questions from a new user

Subject: Re: [Boost-build] Questions from a new user
From: JP Cimalando (jp-dev_at_[hidden])
Date: 2017-09-05 04:08:46

On Mon, 4 Sep 2017 12:03:16 -0500
Rene Rivera via Boost-build <boost-build_at_[hidden]> wrote:

> First, welcome to B2 :-)

Thanks for helping.

> Second, are you getting B2 from the develop branch, or some place
> else?

I began with the version included in boost 1.63.0 which my Linux ships,
then moved to git master to check if it would fix my cross-compiler
trouble. That's still my current version as of now.
I also have a VM for Visual Studio which has 2016.03.
(if that's of any interest I published a script for windows binary
installer, here https://git.io/v5zvg)

> Can I quote you on that? For publicity that is. I'm keeping track of
> such quotes for future use on the web site.

Sure, please do.

> # Regular host-os is target-os compiler..
> using gcc ;
> # Cross compiler..
> using gcc : : i686-w64-mingw32-g++ : : <target-os>windows ;
> 
> And doing "b2 toolset=gcc target-os=windows" should pick up the
> second one. If you only have gcc, you can even leave out the
> "toolset=gcc" argument.

It feels like being on right track yet I still can't make this work.
Looking at outputs of "b2 -d2" I obtain completely mixed up compiler
commands.

using gcc ;
using gcc : : i686-w64-mingw32-g++
 : : <target-os>windows ;
using gcc : : x86_64-w64-mingw32-g++
 : : <target-os>windows <address-model>64 ;

"b2 target-os=windows" gets me commands such as
    "g++" "i686-w64-mingw32-g++"   -O3 [....]
and the same with "address-model=64" added
    "g++" "i686-w64-mingw32-g++" "x86_64-w64-mingw32-g++"   -O3 [...]

> You can do this (with the current develop branch of gcc)
It is for gcc only right? (clang seems to reject such an option)