Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40157
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.171 as permitted sender)
Message-ID: <00b801c90ab3$61191fb0$84fc1f3e@foxbox>
To: "Pierre Joye" <pierre.php@gmail.com>,
	"Greg Beaver" <greg@chiaraquartet.net>
Cc: <internals@lists.php.net>
References: <48B955FD.804@chiaraquartet.net> <fe05d1540808300748j3e74ac37xf94d4583ea39cba@mail.gmail.com>
Date: Sat, 30 Aug 2008 16:16:28 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] phar in win32 snapshots
From: steph@php.net ("Steph Fox")

>> Is there a reason phar is built shared in win32 snapshots even though
>> the default in config.w32 is to build it statically?
>
> The default config.w32 (besides being wrong) is shared.

ARG_ENABLE("phar", "disable phar support", "yes");

I'm still not in a position to test and uncover what you might mean by 
'wrong' - just no time these days to spend however long it takes to install 
a new compiler while backing up the old and etc etc etc. I do know, though, 
that it all worked fine before the build system was 'upgraded' and several 
of the other config.w32 files across the core were 'fixed' to accommodate 
those changes.

> Why should it be built statically?

Because that's what it says in the config file. Unless you've altered 
ARG_ENABLE() to mean something different?

- Steph