Re: [Boost-users] [boost-newbie] g++ Version 3 (MinGW) and compiling boost

Hi Jürgen, Am 24.09.2011 11:34, schrieb Jürgen Hunold:

Hi Robert,

On Friday, 23. September 2011 22:08:23 Robert Hartmann wrote:

...

Hi there, does anyone could say me how can I compile Boost.Filesystem with MinGW:

For start, mingw 3.4.2 is _ancient_.

If possible, please get a recent 4.6.x.

I had some difficulties in updating to a more recent MinGW 4.5.x.

...

Is something wrong with my b2-call see below,

there are some issues.

...

or is my project-config.jam buggy?

No, looks fine.

thank you for checking this:-) [...]

...

I got as error message for Boost.Filesystem:

./boost/filesystem/v3/config.hpp:49:5: #error Configuration not supported: Boost.Filesystem V3 and later requires std::wstring support

That means Boost.Filesystem V2 should work?

There are issues with mingw 3.4.2 due to the missing std::wstring support. A look at the mailing list archives might help

...

Can I compile it without other boost things?

Yes, use --with-filesystem and look a the docs for how to select Boost.Filesystem V2

:-) I will try this.

...

I run set BUILDPATH=G:/Downloads/Libraries/boost_1_47_0/ownbuild set INSTALLPATH=G:/Downloads/Libraries/boost_1_47_0/distrib b2 --prefix=%INSTALLPATH%/libs/boost-1.47.0/distrib ^ --toolset=gcc ^ --build-dir=%BUILDPATH% ^ --layout=versioned ^ --variant=debug,release ^ --runtime-link=static ^ --link=shared,static ^ --threading=multi ^ --without-mpi ^ --without-python stage>build.log 2>&1

half of the options have to much "--"

it should be

toolset=gcc ^ variant=debug,release ^ runtime-link=static ^ link=shared,static^ threading=multi ^

Well, than I had misread/misunderstood some helpfiles and tutorials.

...

And in build.log I found many errors after waiting some Minutes:

...failed updating 26 targets... ...skipped 30 targets... ...updated 842 targets...

26 targets looks fine for Boost.FileSystem.

You mean that these 26 targets were Boost.FileSystem and all others were ok?

...

If I doesn't use the options --without-mpi --without-python than about 30 seconds later I got this output in build.log:

======================

G:/Downloads/Libraries/boost_1_47_0/tools/build/v2/build\virtual-target.jam :1079: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target:mpi.pyd

Interesting. Seems that mpi is build in two variants resulting in the same pyd. Splitting up your build is the easiest way around this.

But you need Python working with mingw 3.4.2, too.

Good point. I thought I could use some Python (which is not from mingw).

...

Please, can any one help me?

Hope this helps.

You helped me. Danke sehr :) Best regards, Robert Hartmann