Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13641 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 611 invoked by uid 1010); 31 Oct 2004 06:15:22 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 426 invoked from network); 31 Oct 2004 06:15:20 -0000 Received: from unknown (HELO caraveo.com) (216.232.147.41) by pb1.pair.com with SMTP; 31 Oct 2004 06:15:20 -0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by caraveo.com (Postfix) with ESMTP id 5E25AD39B1; Sat, 30 Oct 2004 23:15:20 -0700 (PDT) Message-ID: <418482F7.4050708@caraveo.com> Date: Sat, 30 Oct 2004 23:15:19 -0700 User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrei Zmievski Cc: internals@lists.php.net References: <39F7BCBE-29F5-11D9-88E3-000D93B4252E@gravitonic.com> In-Reply-To: <39F7BCBE-29F5-11D9-88E3-000D93B4252E@gravitonic.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP_SHLIB_SUFFIX and OS X From: shane@caraveo.com (Shane Caraveo) 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. Andrei Zmievski wrote: > 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 library, and this option seems to be configured by default (i.e., I > didn't do anything to specifically enable it during buildconf/configure > stage). However, we define PHP_SHLIB_SUFFIX to always be .dylib on OSX > and the portability of scripts breaks in this case. Any suggestions? > > -Andrei >