From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-12-11 00:07:27
David Abrahams wrote:
> Tonight I decided to test against a MinGW compiler. I added
> using gcc : mingw : /tools/MinGW/bin/g++.exe ;
> to my user-config.jam
> Then I tried
> bjam --toolset=gcc-mingw
> and all heck broke loose. It actually issued commands that looked
> "c:\tools\MinGW\bin\g++.exe" "g++" ...
Wow! Weird :-\
> Eventually, with no assistance from documentation, I figured out that
> I couldn't call my toolset gcc-mingw. So I renamed it:
> using gcc : 3.4.2 : /tools/MinGW/bin/g++.exe ;
> bjam gcc-3.4.2
> works as expected except that I see gcc-mingw-3.4.2 in target paths.
That would be the "flavor" feature being injected to distinguish the
MinGW specific GCC version.
> What would I do if I also had a cygwin gcc-3.4.2 installed? I don't
Just treat it as a regular Unix gcc:
using gcc : : /path/to/g++
And build with:
If you also had the MinGW version set up you could:
> Since I do see gcc-mingw-3.4.2 in my target paths, I thought I'd try
> bjam gcc-mingw
> which again breaks in a strange way.
> What all of this does and how to use it needs to be explained and
> documented by someone who understands it.
That would be me... But I must confess, I just dread having to edit the
BBv2 BoostBook documentation files. I have no clue where to put things
and writing docs in XML is among the most painful tasks I can think of.
-- -- 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