Boost logo

Boost-Build :

From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2008-03-23 08:29:39

Today I wanted to try out mingw 4.2.1.
The compiler works almost well with boost-build,
but one (minor?) problem persists:

If I have not set up the environment path beforehand
so the g++ find its bin directory, some components, such as
the as cannot be found properly.

One could argue that it obviously is necessary to set
up the environment correctly. But not when using
boost-build I think. Boost build should be able to
set up different environments since it is able to
request builds of multiple compilers in one run.

This is similar to msvc, where a vcvars.bat file is
run before compiler invocation, such as to make correct
paths and the like.

mingw 3.4.5 had no problems in this respect since it
was able to pick up everything from the initial command
invocation. Unfortunately not mingw 4.2.1. And I also
cannot see that it would be wrong behavior either.
A correct environment is duty of the build system.

So my questions are:

1) Is there a simple trick I could use to adjust the PATH
   before every invocation?
   using gcc
       : 4.2.1
       : "SET PATH=C:/mingw-4.2.1/bin;%PATH% && g++-sjlj.exe"
       : <flavor>mingw
       : <root>"C:/mingw-4.2.1/"
       : <cxxflags>-fno-strict-aliasing
   does not work, because bjam complains about too long command line.

2) Is there another solution? Am I thinking into the wrong

Thank you!

  _  _  | Roland Schwarz
 |_)(_  | aka. speedsnail
 | \__) | mailto:roland.schwarz_at_[hidden]

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at