Re: [INTERNALS-WIN] Build Windows PHP5.3 extension to work with Apache 2.2

hi Chris,

On Wed, Sep 30, 2009 at 9:31 PM, Chris Kukuchka <[email protected]> wrote:
> Pierre, Andy,
>
> Thank you both for your responses.  They are very much appreciated.
>
> Using Pierre's suggestion, I was able to take the VC9 Apache build from
> Apache Lounge and match that up with the thread-safe VC9 build of PHP.
>  After a few configuration flag changes in my VC9 PHP build environment, I
> produced a PHP extension which works quite nicely.

good news :)

> One issue I did need to work around was getting my source files to detect
> values set during configuration.  It seems to not work the same as previous
> versions.  Traditionally, inside my config.w32 file is this logic:
>
> <from config.w32>
> if (PHP_FOO != "no") {
> ...
>  if (PHP_APACHE2_2HANDLER!="no") {
> ...
>     AC_DEFINE("FOO_APACHE", 1, "Build FOO with Apache support");
>     STDERR.WriteLine("Notice: " + "Building FOO extension with Apache 2.2
> support");
> ...
>   }
> ...
> }
> </from config.w32>
>
> In the past, the above logic set a define called FOO_APACHE using the
> AC_DEFINE configuration directive.  This define could be detected during the
> build.  I used that flag within my source code to control various code
> features.  For instance, this code is from the extension header file:
> However, with this new build environment, it does not appear to be passing
> that define into the Makefile.  It is possible this is my first Apache
> target using a Windows build and I am simply trying to equate a
> non-compatible concepts from phpize and config.m4.  However, this is
> something I was looking to have supported and did not function.
<snip>
> Is this something that needs to be handled differently or is it just not
> supported for the Windows build environment?

That should work, we use this syntax in many places. Are you sure that
the conditions are valid?

Cheers,
-- 
Pierre

http://blog.thepimp.net | http://www.libgd.org