Andrei posted this a while ago, but nobody replied and we have learned
this is it not possible.

With the current state of the code and configuration system what would
it take to do something like this:

Core PHP code is built into libphpX.so (libphp4.so)

All SAPI's require libphpX.so:

libphpX_apache.so <- apache sapi
libphpX_embeded.so <- apache sapi

and the command line sapi would have a depenency on libphpX.so.

Brian

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

I guess not too many people are interested in something like this..

- Andrei

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

I remember a thread about this about a year ago. Sascha's answer was
something along the lines of 'build it twice if that's what you want'.
Can't find the thread though.

George

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Hello Brian,


Sounds nice to me. But are you willing to work out a patch for that so that
we can play with it? Or do you anyone in mind who could do that change and
has some time for it?


Best regards,
Marcus mailto:helly@php.net

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

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.

--Jani


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

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?

- Andrei

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

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, Germany

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Well, maybe we can have a ZTS and a non-ZTS version of the core lib.

- Andrei

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

That seems like a nice standard way of handling it.

George

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

That is also how the new win32 build system handles it;
you have the option of php5ts.dll or php5.dll.

--Wez.


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php