Re: [Boost-build] mingw 32 and 64 bit targets

Subject: Re: [Boost-build] mingw 32 and 64 bit targets
From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2015-08-19 03:50:34

Am 19.08.2015 um 08:43 schrieb Vladimir Prus:
> You should be able to do what you did before - the configuration checks
> are done
> for the toolset that targets are generated for, so the usual ways of
> specifying
> the toolset continue to work.

Sorry, this does not work for me :-(

Hmm somehow the current behaviour (dependence on the order of compilers
in the *-config.jam) remembers me of a problem I had for the previous
upgrade. When I had the Visual compiler as the first one in my
user-config.jam some tests (don't remember which) were always done for
this default compiler although I was requesting a gcc toolset, with the
consequence of not being to able to compile. The only remedy was to
reorder the compilers, but I never found out what the problem was. I
also remember that you had a vague idea of what could be going on and
suspected that a solution would require quite a lot of work. Can it be
the case that the same problem is affecting me here?

Using the suggestion from Edward i.e. tweaking the version number as
e.g.  "4.8x64" improves the situation. But now I get neither 32 nor 64
bit test signalling true. At least the compile keeps going. Well I hit
another (unrelated) problem because I am currently using the mingw-w64
toolchain based on win32 thread API which has no call_once support (yet?).

I could use a work-around in having one config per compiler (tested for
one compiler so far) but this looks rather awkward.

Seemingly mingw isn't all too well supported ...

Roland