Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27290
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain krug.dk from 192.38.9.232 cause and error)
Message-ID: <459F1C08.7040300@krug.dk>
Date: Sat, 06 Jan 2007 04:48:24 +0100
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: PHP Internals List <internals@lists.php.net>
OpenPGP: id=157D0FA8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Windows build
From: edin@krug.dk (Edin Kadribasic)

Hey,

It seems that VC++ 8.0 (Visual Studio 2005) brings more trouble that its
worth. Mainly the way it deals with the C runtime. After spending hours
and hours of trying to figure out the way to make PHP work under Apache
on Windows and be able to load extensions, I'm throwing in the towel.

I can get PHP to work fine on the command line, both cgi and cli. It
also works fine under IIS using fastcgi. But loading sapi dll into a
webserver (not using php.exe or php-cgi.exe) works for the sapi itself,
but trying to load any extensions via php.ini fails miserably. Sometimes
you will get an error that the C runtime was attempted to be loaded in
an illegal way, sometime PHP will claim that the extension does not
exist, etc.

I looked around at other projects and everyone seems to be using VC++
6.0 for their builds (Active state, apache, ...) which eliminates all
the hassle with bundling C runtime, etc.

So I think the best thing for us would be to stick to the good old C
compiler for making the Windows distro.

Edin