Re: Re: Enabling opcache causes libraries to build as static
| From: | Johannes Schlüter | Date: | Sun, 13 Mar 2016 14:01:30 +0000 |
| Subject: | Re: Re: Enabling opcache causes libraries to build as static | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-91648@lists.php.net to get a copy of this message | ||
On Tue, 2016-03-08 at 15:18 +0000, Andrea Faulds wrote:
> While we're at it, why is Opcache still built as shared? Does
> something
> prevent it being statically-linked?
The reason for this is that opcache is no "PHP module" but a "Zend
Extension" and we simply don't have an initialization mechanism for
static Zend Extensions. Such a mechanism would require to create an
extension list, similar to the module list in main/internal_functions.c
from the build system (see configure.in and .win32/build/confutils.js)
and then invoke them somewhere around
zend_startup_extensions_mechanism(), zend_startup_extensions() and
zend_shutdown_extensions().
Should be quite straight forward to do (for somebody willing to dig into
both, autofoo and our Windows build system)
johannes
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc