Hi folks,
is it already possible to build the sapi modules separately ?
I'd like to split them off into completely separate packages
for easier systems maintenance.
cu
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
is it already possible to build the sapi modules separately ?
I'd like to split them off into completely separate packages
for easier systems maintenance.
Various distros already do this. See for example the Red Hat PHP RPM. It
depends which packaging system you use, but if you're familiar with RPM
then this would perhaps be a good starting point.
Dave
is it already possible to build the sapi modules separately ?
I'd like to split them off into completely separate packages
for easier systems maintenance.Various distros already do this. See for example the Red Hat PHP RPM. It
depends which packaging system you use, but if you're familiar with RPM
then this would perhaps be a good starting point.
They are still building SAPIs as part of the main PHP build.
Building "stand-alone" SAPIs is not really supported. The closest one
can do is build the embedded SAPI and then link against the created lib
(either .a or .so) I was successful in the past ignoring the "embedded"
stuff in the lib and register your own SAPI. But as said: That's not
really supported.
For this reason we're a bit less strict about adding SAPIs, like we did
with lightspeed and fpm.
johannes