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
