Andi Gutmans wrote:
> >OK, my mistake. So moving php4/ext/midgard to php4/pear/midgard would
> >solve this?
>
> Well right now it won't really solve it because pear is included in the
> distribution. However, the idea behind pear is to be something more similar
> to CPAN which means both PHP and C code.
OK, but CPAN is huge too.
> >Does the build process differ here? And like my previous question, are
> >there
> >examples on how to build config.m4s, and other supportive files, so an
> >extension can easily be built as an php-dloabable, a static extension,
> >and a static extension in a statically-compiled PHP (into Apache
> >itself)?
>
> The easiest way to get it working is "cd php4; cp -r /path/to/midgard ext;
> ./buildconf".
> That's all people need to do in order to get it to work with their vanilla PHP.
> You can check out some of the other extensions to see how to build a shared
> library but with my example it's not necessary.
What I couldn't find there is how to detect that we're being built
using apxs or statically in apache, for example.
> There is also the phpize stuff (which I don't know). It's something like
> phpize /path/to/midgard and then compiling the midgard as a shared library.
> I think the first example I gave you is probably good enough though.
The phpize methods works (it's what we use right now), but loading the
midgard extension for every request does not have my preference.
Emile
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
