Boost logo

Boost :

From: Jesse Jones (jesjones_at_[hidden])
Date: 2001-11-07 21:43:54

At 9:32 PM -0500 11/7/01, Beman Dawes wrote:
>At 07:51 PM 11/7/2001, Jesse Jones wrote:
> >This worked for me. It looks like the thread library built OK
> >although there were 20 or so warnings. The static regex libraries
> >were built as well, but the shared libraries failed to build (OS X's
> >shared library support is a bit unusual I think). The python
> >libraries failed to build because I installed Python with Fink which
> >puts stuff in /sw instead of /usr. But the thread library is all I'm
> >really interested in right now so I can start wrestling with the GNU
> >auto* tools again. :-)
>We are really interested in user experience reports for the thread
>library. That's also true of the rest of the libraries, too, but because
>of portability questions it is particularly true of threads.
>So please send in a report of your OS X experiences, good, bad, or

I'm still trying to get my make files past automake so I don't have a
lot to report yet. I did build the thread library with CodeWarrior
though. If you target Mach-O (as opposed to CFM) pthreads are
available, but the configuration headers don't catch this. I added
the following to the metrowerks.hpp file:

#include <cstddef> // include a light-weight header
#ifdef _BSD_PTRDIFF_T_ // check for one of the BSD Unix defines
     #define BOOST_HAS_THREADS // if we found it assume we're targeting Mach-O

This is a little lame, but Metrowerks doesn't seem to provide a
predefined macro to signal that Mach-O is being targeted.

   -- Jesse

Boost list run by bdawes at, gregod at, cpdaniel at, john at