Hi,
I just committed to ext/phar's config.m4/w32 to make phar enabled by
default as a shared extension. This is a better default setting than
building phar in statically, as phar has optional dependencies on the
zlib and bz2 extensions to enable compressed phar archives. If phar is
built statically, then it would require both zlib and bz2 to be built
statically in order to use them, something that is obviously not going
to happen, as they have been around a while and nobody has even
suggested it (to my knowledge). Having phar shared means one can easily
plug in zlib/bz2 support without recompiling PHP.
I'm open to further input/tweaks on this decision. If you have a better
idea, go ahead and commit to phar's config.m4/w32, these files are very
easy to change if needed.
Greg
Hello Gregory,
aren't we simply using streams here only? If so we can still build phar
statically with I'd prefer very much. And the streams stuff would be found
if present. The optional dependency would then ensure correct load order.
marcus
Friday, May 16, 2008, 2:05:35 AM, you wrote:
Hi,
I just committed to ext/phar's config.m4/w32 to make phar enabled by
default as a shared extension. This is a better default setting than
building phar in statically, as phar has optional dependencies on the
zlib and bz2 extensions to enable compressed phar archives. If phar is
built statically, then it would require both zlib and bz2 to be built
statically in order to use them, something that is obviously not going
to happen, as they have been around a while and nobody has even
suggested it (to my knowledge). Having phar shared means one can easily
plug in zlib/bz2 support without recompiling PHP.
I'm open to further input/tweaks on this decision. If you have a better
idea, go ahead and commit to phar's config.m4/w32, these files are very
easy to change if needed.
Greg
Best regards,
Marcus