Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49911
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: Dave Ingram <dave@dmi.me.uk>
Cc: weigelt@metux.de, php-dev <internals@lists.php.net>
In-Reply-To: <4CB83A8B.1000600@dmi.me.uk>
References: <20101014110444.GA14927@nibiru.local>
	 <4CB83A8B.1000600@dmi.me.uk>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 15 Oct 2010 13:44:22 +0200
Message-ID: <1287143062.5215.107.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] build sapi's separately
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2010-10-15 at 12:27 +0100, Dave Ingram wrote:
> On 10/14/10 12:04, Enrico Weigelt wrote:
> > 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