ilto:[EMAIL PROTECTED]
> Sent: Saturday, November 06, 2004 6:44 PM
> To: [EMAIL PROTECTED]
> Cc: Andrei Zmievski; Shane Caraveo
> Subject: Re: [PHP-DEV] PHP_SHLIB_SUFFIX and OS X
>
>
> I guess I'm stepping in, in the middle of the conversation,
> but dylibs and so's are
I guess I'm stepping in, in the middle of the conversation,
but dylibs and so's are totally different on MacOSX.
One of those OS X MACH-O oddities.
.dylib's are libraries which you link against, and are loaded at
runtime. (Shared Library)
.so's are something you can dlopen() (as of 10.3, don't reme
Sticking with .dylib across the board is fine with me, but try telling
that to libtool. For some reason it wants to stick to .so extension,
instead of .dylib and I just do not have the time or effort to debug
the beast that is libtool. Any hints on how to make it use .dylib?
-Andrei
On Oct 30,
Not a real suggestion, but a comment on this...
There is no reason to use dylib for libraries that will only be loaded
by php. the php library itself should be .dylib, by php extensions
*can* be .so. Python works this way. However, I'm not convinced it's
the best thing, as it does lead to fur
I've been trying to build PHP-GTK on OSX and ran into something. The
GNU libtool can create shared libraries both with .so and .dylib
extensions, depending on whether they are compiled as modules or
libraries that can be linked against. If -module is specified for
libtool, it'll link an .so lib
