Re: Interest in a "null" SAPI for embedding?
| From: | Johannes Schlüter | Date: | Mon, 19 Aug 2013 23:49:14 +0000 |
| Subject: | Re: Interest in a "null" SAPI for embedding? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-68575@lists.php.net to get a copy of this message | ||
On Mon, 2013-08-19 at 19:17 -0400, J David wrote:
>
> To stick with your example, of CLI and mod_php -- a good choice as
> it's likely the most common combo -- when linking to a common
> libphp5.so, the recommended methodology would be to build in only the
> functionality required by both, then load the rest as extensions from
> php-cli.ini or php.ini, respectively. This seems like the way it is
> generally done anyway?
>
> Is doing it this other way a thing that people actually do?
Ah, there's another thing to mind: Extensions can be marked as "cli
extensions", if statically compiled they become only part of the CLI
binary, not other SAPIs. Think readline & pcntl.
johannes