On Wed, 09 Jul 2008 08:27:39 +0100, Anthony Williams
First off, put threadapi=win32 on your bjam command line. This will ensure the libraries are named differently to the pthread ones, and won't define the macros that force pthreads.
Next, ensure that _WIN32 is defined (e.g. add -D_WIN32 to <compileflags> for your compiler in user-config.jam)
I wouldn't recommend trying to use some pthreads and some win32 builds of boost libs in the same app: if they use any boost.thread facilities then the definitions are different between the two APIs (e.g. structure of boost::mutex).
Good point. And building boost with winegcc adds a whole secondary translation layer which bypasses any optimizations the boost developers have done.
From queries to the wine-devel list, the problem is that Wine needs to know about threads being created. So I might be able to work with that.
Thanks for the help... mo