Re: Compiling 2 SAPIs
| From: | Jani Taskinen | Date: | Wed, 28 Jan 2004 06:56:15 +0000 |
| Subject: | Re: Compiling 2 SAPIs | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-7368@lists.php.net to get a copy of this message | ||
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.patchN€
r’“þ
>> ã=ž6b«˜
>>
>> 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