Re: always building executable
| From: | Stig S. Bakken | Date: | Tue, 16 Oct 2001 00:05:49 +0000 |
| Subject: | Re: always building executable | ||
| References: | 1 2 3 4 5 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-67997@lists.php.net to get a copy of this message | ||
"Stig S. Bakken" wrote:
>
> Andrei Zmievski wrote:
> >
> > On Mon, 15 Oct 2001, Stig S. Bakken wrote:
> > > If you make it a normal extension, and you don't have --enable-pcntl in
> > > your configure line, the right thing would be to include it in the cli
> > > version but not the apache version or whatever. So either we need a
> > > mechanism for conditionally including extensions in a build (ka-yuck),
> > > or it has to be moved.
> >
> > But what about other extensions that only make sense with cli version,
> > like readline?
>
> Hm, good point, there are lots of these. So basically we need another
> library aside libphp4.la for each sapi backend, and put the extensions
> in question into the right one of these.
That was really a write-only reply. :-)
What I mean is something like this (SAPI means selected SAPI backend):
libphp4core.la - "core" library (main, libs, expat, regex etc)
libphp4ext.la - extensions in all sapi backends
libphp4ext_apache.la - extensions for use with sapi/apache
sapi/apache/libphp4.la - final Apache library
- Stig