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

Subject: Re: [Boost-build] Questions from a new user
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2017-09-07 15:14:06

On Mon, Sep 4, 2017 at 11:08 PM, JP Cimalando via Boost-build <
boost-build_at_[hidden]> wrote:

> On Mon, 4 Sep 2017 12:03:16 -0500
> Rene Rivera via Boost-build <boost-build_at_[hidden]> wrote:
>
> > # 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 [...]
>

Do you get the same results if you use the "develop" b2 version?

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

Yes, it's only for gcc at the moment. I'm planning a clang rewrite soon
though. So I'll add that option in at that point.

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail