This method compiles the libphp directly into the Apache binary, thus it is
'supposed' to be faster.  The problem is the negative side of doing this.
With PHP's frequent releases, a user would need to be re-compiling Apache
each time a new build of PHP was being installed (thus the reason most ISP's
do NOT upgrade each time).

I prefer to conf php as a DSO...this way it's quite simple to upgrade php
each time without affecting apache at all.

Thanks,
JT

-----Original Message-----
From: Ken Jeansson [mailto:k.jeansson@[...].com] 
Sent: Wednesday, August 14, 2002 10:23 AM
To: php-install@[...].net
Subject: [PHP-INST] This VS that?

I was reading through the installation help on php.net and noticed this
little option for configure

./configure --with-apache=/path/to/apache_source

And the text that follows.

"This will create a libmodphp4.a library, a mod_php4.c and some accompanying
files and copy this into the src/modules/php4 directory in the Apache source
tree. Then you compile Apache
using --activate-module=src/modules/php4/libphp4.a and the Apache build
system will create libphp4.a and link it statically into the httpd binary."

Now, is there anything to be won with using this method than the "usual" (in
my case ./configure --with-apxs2=/bla/blabla?

// Ken



-- 
PHP Install Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

-- 
PHP Install Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php