From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-12-15 12:35:48
Roland Schwarz wrote:
> David Abrahams wrote:
>> Eventually, with no assistance from documentation, I figured out that
>> I couldn't call my toolset gcc-mingw. So I renamed it:
> I just discovered another potential problem if the mingw cannot be
> uniquely identified:
> I needed to specify the mingw compiler in the explicit-failures-markups.xml.
> It is unclear to me how to name the toolset correctly in this context:
> gcc-mingw ?
Yes. One always needs to use the full name of the toolset in the
failures markup. This was one of the issues we resolved for BBv1 vs.
BBv1. BBv2 attempts to make those names consistent. For example:
<http://tinyurl.com/tfs4o>, <http://tinyurl.com/yxxzls>, and
<http://tinyurl.com/y72wn3> are the MinGW toolsets that are currently
being tested for 1.34.
Also of note is that for conditions, i.e. for specifying compilers
specific build options, in Jamfiles one can use "gcc" to refer to all
flavors of GCC. And use "gcc-mingw" to refer to only the MinGW flavor.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk