Re: Compiling 2 SAPIs
| From: | Uwe Schindler | Date: | Tue, 27 Jan 2004 16:57:22 +0000 |
| Subject: | Re: Compiling 2 SAPIs | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-7358@lists.php.net to get a copy of this message | ||
At 17:40 27.01.2004, you wrote:
On Tue, 27 Jan 2004, Jani Taskinen wrote:Would be great. The only thing is: We must compile all SAPIs with ZTS enabled... But thats the same on windows. ----- Uwe Schindler thetaphi@php.net - http://www.php.net NSAPI SAPI developer Erlangen, GermanyHere's what I came up with:http://www.php.net/~jani/patches/multi_sapi_build.patchWith 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. 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?