On Sep 25, 2009, at 11:06 AM, Yang Tse wrote:
The code now compiles and works properly on OS X and reasonably modern Linuxes with pthreads. Additionally, I've reworked the configure script so that it will choose threaded resolve when pthreads are available but c-ares is not. I've also regression tested the whole thing on Windows XPand above.Right now libcurl is already capable of being used in multi threaded apps out of the box, no matter if the binary library is linked with a program that uses native threads or POSIX threads. IOW libcurl is not dictating which thread library must be used. If this is changed and libcurl would be linked with the pthreads library by default, when available at compile time, apps linking to libcurl would necessarily need to be linked with the pthreads library as well as _all_ libraries used by libcurl. I don't foresee a pleasant future if the change affects the default libcurl building. I think that forcing a specific default threads library down on everyone is not a good thing. As an option that anyone could choose I have no objection at all.
FWIW, libpthread isn't always a separate library. On Mac OS X it's part of libSystem which is what Apple calls its libc, and so always available. But it should be optional in any case.
Daniel
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
