boost-users-bounces@lists.boost.org wrote:

Ok the mist is rasing ;-)

There should be no problem mixing pthread and Boost.Thread. I.e. your inherited lib can use pthread while your new code can use Boost.Thread on the native API.

I agree. But I have to deal with a great fear factor here. People think there will be a problem and the only way to deal with it is to (truthfully) say that everything is using the win32 port of pthreads. It is the only approach that will be accepted :-(

But if on the other hand for whatever reason you want to take the additional (IMHO unnecessary step) to build boost thread on top of pthread you can. Here is how we go:

Open the file BOOST_ROOT/libs/thread/build/threads.jam Follow the instructions found there and set up your environment variables accordingly.

Excellent. This is exactly what I was looking for. Thanks very much, I will give this a try.

Again the whole mess isn't worth doing it.

Technically, I agree. Politically......deep sigh....... The build is now in progress and it is time for me to go home and eat more mince pies :-) I will pick up on this again in the New Year. Many thanks again and Happy New Year! -Andrew Marlow ******************************************************************************" The data and information (collectively called Information) herein is the sole property of ICAP. The Information is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. Unauthorised disclosure, copying or distribution of the Information is strictly prohibited and the recipient of the Information shall not redistribute the Information in any form to a third party. If you received this Information in error please tell us by reply (or telephone the sender) and delete all copies on your system. References in this Information to ICAP are references to ICAP plc, a company incorporated in England with registered number 3611426 whose registered office is 2 Broadgate, London, EC2M 7UR and where the context requires, includes its subsidiary and associated undertakings. As applicable, certain companies within the ICAP group are authorised and regulated by the Financial Services Authority. Any investment research sent from ICAP will provide an impartial and objective assessment of the securities, companies or other matters that are the subject of their research and our Conflicts of Interest Management Policy regarding investment research can be viewed by requesting a copy from your usual contact at ICAP. Please visit www.icap.com for further regulatory information including details regarding the European eCommerce Directive. *******************************************************************************" We have taken precautions to minimise the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. " *******************************************************************************