Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27303
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 81.169.182.136 cause and error)
Date: Sat, 6 Jan 2007 20:48:23 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1565089753.20070106204823@marcus-boerger.de>
To: Ilia Alshanetsky <ilia@prohost.org>
Cc: Edin Kadribasic <edin@krug.dk>,
	PHP Internals List <internals@lists.php.net>
In-Reply-To: <618CF1AA-CBDB-4863-9EFF-7A766D23819C@prohost.org>
References: <459F1C08.7040300@krug.dk> <618CF1AA-CBDB-4863-9EFF-7A766D23819C@prohost.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Windows build
From: helly@php.net (Marcus Boerger)

Hello Ilia,

  weel 2002 aka 7.0 or 2003 aka 7.1 are pretty fine. We have left behind
6.0 long ago :-)

best regards
marcus

Saturday, January 6, 2007, 5:44:55 AM, you wrote:

> Edin,

> Thanks for the detailed analysis and spending time analyzing the  
> issue. Based on what you've said I think our best option is to go  
> back to VC++ 6.0 for this release, we are too far along in the  
> release cycle to experiment with things. Perhaps for the next release  
> we can revisit the issue, assuming there an interest and a benefit of  
> using VC++ 8.0 can be quantified.

> On 5-Jan-07, at 10:48 PM, Edin Kadribasic wrote:

>> 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.

> Ilia Alshanetsky




Best regards,
 Marcus