Re: phar in win32 snapshots

Pierre Joye wrote: > hi, > > On Sat, Aug 30, 2008 at 6:41 PM, Greg Beaver <greg@chiaraquartet.net> wrote: > >> Pierre Joye wrote: >> >>> hi, >>> >>> On Sat, Aug 30, 2008 at 4:15 PM, Greg Beaver <greg@chiaraquartet.net> wrote: >>> >>> >>>> Hi, >>>> >>>> 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. >>> >>> Why should it be built statically? >>> >> It builds statically in vs 2008 with PHP_5_3 on my box, you are >> mistaken. For reasoning on static build, see the list archive. >> > > Can you try to actually what is used to build a release please? > > cscript /nologo configure.js --enable-snapshot-build --enable-debug-pack > > And I still have no answer to my question. Why should it be built statically? > > The change has been introduced with the extension dependencies patch > (or in the same period, to be checked, post alpha2 anyway). Hi, Right, my point is that this: configure --enable-debug-pack builds phar in statically, just as zlib is built statically. Perhaps the --enable-snapshot-build could be fixed to match this behavior? It makes it hard to design config.w32 for multiple branches if it behaves differently with different unrelated config options. Thanks, Greg P.S. I'm not trying to start a war over anybody's code religion, just asking for an obvious bug in the build process to be corrected.