Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7368 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5643 invoked by uid 1010); 28 Jan 2004 06:56:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 5590 invoked from network); 28 Jan 2004 06:56:17 -0000 Received: from unknown (HELO smtp3.pp.htv.fi) (213.243.153.173) by pb1.pair.com with SMTP; 28 Jan 2004 06:56:17 -0000 Received: from localhost.localdomain (cs181008.pp.htv.fi [213.243.181.8]) by smtp3.pp.htv.fi (Postfix) with ESMTP id 6175727B041; Wed, 28 Jan 2004 08:56:16 +0200 (EET) Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.10/8.12.10) with ESMTP id i0S6uFpn013757; Wed, 28 Jan 2004 08:56:15 +0200 Date: Wed, 28 Jan 2004 08:56:15 +0200 (EET) Reply-To: Jani Taskinen To: Andrei Zmievski Cc: internals@lists.php.net In-Reply-To: <20040127164011.GE32706@gravitonic.com> Message-ID: References: <20040127164011.GE32706@gravitonic.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Compiling 2 SAPIs From: sniper@iki.fi (Jani Taskinen) On Tue, 27 Jan 2004, Andrei Zmievski wrote: >On Tue, 27 Jan 2004, Jani Taskinen wrote: >> Here's what I came up with: >> >> http://www.php.net/~jani/patches/multi_sapi_build.patch >> >> With the patch applied, I'm now able to build at least >> apache, cli, cgi and embed SAPIs on one run. >> >> # ./configure --disable-all --with-apxs --enable-embed >> >> (CLI and CGI are build by default..) >> >> I build them using static 'core' lib as I dislike the >> idea of having to install and maintain several libs. :) >> >> But if someone insists, it's possible to build one shared >> lib too..I actually tested with that first. :) > >Does your patch just build multiple SAPIs as separate shared libs or >does it make one shared lib that has multiple SAPIs in it? The latter is >what I want. It creates a static libphp5_core.a which is linked to each build SAPI module / binary. Dunno how you could have same lib loaded by e.g. Apache / Apache2 ?? Or what did you mean? :) >The best (ideal) result would be to have one libphp[45].so that contains >the core. The SAPIs should link against it, so we'd have libphpembed.so, >libphpapache.so, etc. Can this be done? My first tests had the libphp5_core lib as shared..so yes. I'll update my patch a bit. --Jani