Boost logo

Boost-Build :

Subject: [Boost-build] Boost 1.43 Install problems under Mingw32
From: Kai Henningsen (kai.extern_at_[hidden])
Date: 2010-08-15 12:00:58


First, the bootstrap breaks when compiling bjam. The reason for that
is that bootstrap.sh forces toolset gcc on the build; the
auto-detected toolset mingw would have worked.

Workaround:

./bootstrap.sh --prefix="$EMpfx" --with-toolset=mingw # just for bjam.exe
mv -v ./bjam "$EMpfx/bin"
./bootstrap.sh --prefix="$EMpfx" --with-bjam="$( which bjam )"
bjam
bjam install

Second, it is somewhat irritating that the build machinery does not
understand Msys-style paths (/c/foo for c:\foo). That leads to
hard-to-find install errors when prefix is such a path, stuff ending
up installed in c:\c\foo instead, where people won't even know to
look. At least a prominent warning about this fact would be
appreciated. Possibly, when working with Windows-style paths, complain
if there's no drive letter? That would make it clear that there are
differing expectations. Or something.


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