On Tue, Mar 13, 2001 at 10:45:45PM +0100, Stig Sæther Bakken wrote:
> This is not different from the way it works in PHP. The problem is
> that if you have an extension that uses "phpize" to make its own
> configure script etc, and you want to define your own variables there,
> configure will mak
This is not different from the way it works in PHP. The problem is
that if you have an extension that uses "phpize" to make its own
configure script etc, and you want to define your own variables there,
configure will make a file called "php_config.h". Unless you
explicitly put "." in your inclu
What is the reason for this? Shouldn't we keep it the way it works within
the PHP tree? Some modules include php_config.h or do you also have that in
PEAR?
Andi
At 09:54 AM 3/12/2001 +, Stig Bakken wrote:
>ssb Mon Mar 12 01:54:26 2001 EDT
>
> Modified files:
> /php4/pear
ssb Mon Mar 12 01:54:26 2001 EDT
Modified files:
/php4/pear pear.m4
Log:
HEADS UP: renamed config header file in "phpize"d extensions to
"config.h" rather than "php_config.h".
Index: php4/pear/pear.m4
diff -u php4/pear/pear.m4:1.7 php4/pear/pear.m4:1.
4 matches
Mail list logo