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 remember the 10.2 similar functions)... (Loadable Module)
Please note that these are _not_ interchangeable. You cannot link against a .so, and you cannot dlopen() a .dylib on MacOSX.
If you decide to name all libraries .dylib, even those that are meant to be dynamically loaded via dlopen, you will add a lot of confusion into the mix... which is why libtool is most likely not cooperating.
A good reference on this is here: http://fink.sourceforge.net/doc/porting/shared.php?phpLang=en#lib-and-mod
-Brad
Andrei Zmievski wrote:
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, 2004, at 11:15 PM, Shane Caraveo wrote:
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 further confusion. Sticking with dylib across the board is much clearer.
The only questionable part is the sapi modules, where it would depend more on what is loading the sapi.
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
