Re: 4.3.0 Extension
| From: | Derick Rethans | Date: | Mon, 17 Feb 2003 21:28:30 +0000 |
| Subject: | Re: 4.3.0 Extension | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-94313@lists.php.net to get a copy of this message | ||
On Mon, 17 Feb 2003, md wrote:
> I will look for duplicates as you suggest.
>
> I noticed that you use the PHP_ARG_WITH( inside your website's config.m4
> file.
>
> But if I wanted an internally embedded set of code instead of external
> shared library, I could use PHP_ARG_ENABLE( instead.
That's not the difference. It's just that _WITH creates an extension
that makes use of an external library, while _ENABLE doesn't do that.
You can always install both styles of modules as shared or
static (internal).
> My problem so far has been using PHP_ARG_ENABLE( in config.m4.
>
> Downloading the source tarball, going immediately to ext_skel,
> buildconf, configure, and make has produced the aforementioned error
> in apache.
>
> Somehow, I doubt the ext_skel utility would put 2 of the _confirm_X()
> functions in the same module.
>
> Then comes how the module could be loaded twice when the same apache
> server that runs 4.2.3 is also used to run 4.3.0.
Once statically and once as shared module perhaps?
> I also do not have any idea what the "phpize" is all about, for external
> modules only?
phpize can be used to create shared modules out of the php source tree,
which is often wanted during development. (it's about the same as using
--with-testmodules=shared on your normal php configure line).
Derick
--
Stop mad cowboy disease!
-------------------------------------------------------------------------
Derick Rethans http://derickrethans.nl/
PHP Magazine - PHP Magazine for Professionals http://php-mag.net/
-------------------------------------------------------------------------