Re: [Boost-build] Errors when compiling Boost on Windows with MinGW

Subject: Re: [Boost-build] Errors when compiling Boost on Windows with MinGW
From: Lars Viklund (zao_at_[hidden])
Date: 2012-03-01 10:28:43

On Thu, Mar 01, 2012 at 02:11:32PM +0200, Paul wrote:
> Hi All,
> 
> Thanks for the feedback so far.
>
> On Tue, 28 Feb 2012 15:13:21 +0100
> Lars Viklund <zao_at_[hidden]> wrote:
> > Whatever libraries that successfully builds will be successfully
> > built, and usable.
> Problem is, I'm not sure how fundamental this error is, or which
> libraries it targets. I don't know the error reporting mechanism well
> enough to know if this is a single error, just showing the full call
> stack, or multiple errors.

Whatever library files you have on your filesystem succeeded building.
The ones that didn't won't exist. To find out what library caused what
error, you've got to skim the log to see what files/targets it botches
out on.

A re-invocation should only try to build the things that failed the last
time, narrowing it down.

> > Question: Do we need to specify the toolset explicilty when invoking 
> > bootstrap.bat or not
> Well, when I didn't specify mingw to bootstrap.bat, it complained that
> cl was not a recognised program. For some reason the check for compiler
> wasn't detecting my MinGW, and was trying the VS compiler by default. A
> simple fix, but

The MinGW "autodetection" is limited to looking in a set of predefined
locations and the path, as there's no registry keys or other ancillary
methods of finding it.

A good bet on Windows is to assume that if nothing else works, a flavor
of MSVC might be in the path.

-- 
Lars Viklund | zao_at_[hidden]