Re: cvs: php4 /ext/domxml config.m4 /ext/gd config.m4 /ext/pdf config.m4 /ext/zlib config0.m4
| From: | (Stig Sæther Bakken) | Date: | Mon, 21 May 2001 16:20:31 +0000 |
| Subject: | Re: cvs: php4 /ext/domxml config.m4 /ext/gd config.m4 /ext/pdf config.m4 /ext/zlib config0.m4 | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-5895@lists.php.net to get a copy of this message | ||
[Jani Taskinen <sniper@iki.fi>]
> On 21 May 2001, Stig Sæther Bakken wrote:
>
> >["Jani Taskinen" <sniper@iki.fi>]
> >> sniper Sun May 20 16:00:45 2001 EDT
> >>
> >> Modified files:
> >> /php4/ext/zlib config0.m4
> >> /php4/ext/domxml config.m4
> >> /php4/ext/gd config.m4
> >> /php4/ext/pdf config.m4
> >> Log:
> >> A few modifications to make the ZLIB checks work better.
> >
> >What's the idea behind config0.m4 as opposed to config.m4? To have a
> >file that is included earlier? To make people ask? :-)
>
> This was Sascha's idea, scripts/config-stubs:
>
> #!/bin/sh
> #
> # $Id: config-stubs,v 1.3 2001/05/11 20:09:31 sas Exp $
>
> dir=$1; shift
> for stubfile in $dir/*/config0.m4 $dir/*/config.m4; do
> echo "sinclude($stubfile)"
> done
Yeah, I read that. I still don't understand the motivation though.
Is it for having configure stubs that are included in the static build
but not when using phpize? Sascha?
- Stig
--
Stig Sæther Bakken <ssb@fast.no>
Fast Search & Transfer ASA, Trondheim, Norway