Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:13760
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
In-Reply-To: <418482F7.4050708@caraveo.com>
References: <39F7BCBE-29F5-11D9-88E3-000D93B4252E@gravitonic.com> <418482F7.4050708@caraveo.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-ID: <0076D0DA-3064-11D9-A5B3-000D93B4252E@gravitonic.com>
Content-Transfer-Encoding: 7bit
Cc: internals@lists.php.net
Date: Sat, 6 Nov 2004 18:23:24 -0800
To: Shane Caraveo <shane@caraveo.com>
Subject: Re: [PHP-DEV] PHP_SHLIB_SUFFIX and OS X
From: andrei@gravitonic.com (Andrei Zmievski)

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.