Re: phar in win32 snapshots

Pierre,

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.

Let forget this attempt to yet again discredit the fantastic work being done by the windows team and let us try to figure out what's wrong. The behavior has changed after your dependency patch, the 3rd argument of EXTENSION has to be set to false if the extension has to be built statically.

The Windows team do not have control over all the config.w32 files out in the wild. We don't even have control over all the config.w32 files in PECL. You've now changed the meaning of two functions in the build system to my knowledge, one of which I saw go in and tried hard to get reverted and the other of which I didn't even know about until this moment. My complaints were dismissed out of hand the first time around, and I guess I might as well forget about even trying to complain now, right? I can't believe I'm the only person who sees a problem with this top-down approach to change. Doesn't anyone else even care? - Steph