httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@engelschall.com (Ralf S. Engelschall)
Subject Re: PHP3 (was Re: APACI: Commit Strategy)
Date Mon, 30 Mar 1998 06:08:08 GMT

In article <Pine.WNT.3.96.980329131611.-191397B-100000@shell.lerdorf.on.ca> you wrote:

>> I cannot make such an option because ap_config.h is generated by src/Configure
>> and thus needs to be run completely. Even when APACI would provide a
>> --build-ap-config you gain nothing.  Just running the standard APACI
>> "configure .." command results in the same and is not much slower.
>> 
>> But what I don't understand: Why do you need it? Isn't the mod_php3.c the only
>> source which include it? If this is the case, I see no need for having the
>> ap_config file at hand before building it. Or did I miss something?

> No, it is included whenever any of the Apache header files are included.
> I do need to access r->* from within libphp3.a (now called libmodphp3.a)
> and as such I have to include the Apache header files which means I have
> to include ap_config.h in order for those header files to be correct for
> the platform I am building on.  Putting all Apache-related code in
> mod_php3.c would be a solution.  And in PHP 3.1 this might be possible
> because of a server API abstraction layer we are working on called SAPI.

Moving all those stiff into mod_php3.c would be excellent and very clean.  And
it will avoid problems in the future... Go for it in PHP 3.1.

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com

Mime
View raw message