Re: CLI Sapi automatic build
| From: | Hartmut Holzgraefe | Date: | Mon, 14 Jan 2002 11:33:04 +0000 |
| Subject: | Re: CLI Sapi automatic build | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-77050@lists.php.net to get a copy of this message | ||
Edin Kadribasic wrote:
What is wrong with adding a third parameter to PHP_EXTENSION? If you take a look at the patch, you will see that I need to create a list of libraries that is only built with cli. I don't know how to do that with the two macros you added.you tie ext/pcntl to a certain sapi although it should be available for a certain class of sapis, the standalone ones ext/readline and ext/ncurses are similar cases, they are only usefull in interactive sapis until now both classes had only one member, the cgi sapi right now they have two members, cgi and cli, although cgi should be thrown out as soon as cli is done and ready, but what do we loose if we prepare for additional interactive/standalone sapis by using the checks i added so that we have to do changes in only *one* place instead of changing the calls to PHP_EXTENSION all over the place (not to speak of extension not even in the php4 CVS)? -- Hartmut Holzgraefe hartmut@six.de http://www.six.de +49-711-99091-77