Hi,
as one could already have seen, the links to the extension DLLs has been
integrated into the PECL website. Basically the builds done until now are
shown. Together with the automatic builds this brings automatic updates
for every new release built for windows. A couple of notes I'd like to
bring about this:
- almost latest releases was used for builds
- extensions retaining no compat with windows but potentially compatible
was partly fixed and either pull requests was sent or fixes pushed
directly into repos, where possible, also extension prepared - till now not every extension was built for various reasons
- the legacy unmaintained extensions not compatible with 5.3+ wasn't built
- some exts still miss config.w32 or don't include it into the tarball
- there are of course extensions by design not compatible with windows,
so they couldn't be built anyway - some extensions aren't compatible with all the current PHP branches, so
only links to available builds are shown - library dependencies not (yet) prepared/visual studio incompatible, so
no build - some new releases lost C89 compatibility, so have failed
- nevertheless some extension DLLs aren't shown despite they're
downloadable, as well for various reasons
- extension name is different in package.xml/PECL website/config.w32
(ZendOpcache vs. opcache, xcommerce vs. xcom, etc.), whereby all the
three should be the same (disregarded upper/lower case variant) - an ext is reqiered to have both TS/NTS build to succeed to be shown on
the list of DLL for the particular branch, so builds where only one of
TS/NTS builds is present aren't shown - there are some popular extensions built which aren't registered in
PECL, like twig or facedetect. They're still available for download but
have no PECL page to show them
About 100 worky PECL extension Windows builds are available at the moment.
Given PECL has about 300 extensions registered, that's already a good
start.
After working so much on this matter I anticipate about 50 more extensions
potentially available to the windows users. However some effort will be
still needed to make it possible. For exts missing windows library
dependencies, please just ask. As well for any support regarding windows
build.
Cheers
Anatol
Hello,
2013/10/7 Anatol Belski ab@php.net
Hi,
as one could already have seen, the links to the extension DLLs has been
integrated into the PECL website. Basically the builds done until now are
shown. Together with the automatic builds this brings automatic updates
for every new release built for windows. A couple of notes I'd like to
bring about this:
About 100 worky PECL extension Windows builds are available at the moment.
Given PECL has about 300 extensions registered, that's already a good
start.After working so much on this matter I anticipate about 50 more extensions
potentially available to the windows users. However some effort will be
still needed to make it possible. For exts missing windows library
dependencies, please just ask. As well for any support regarding windows
build.
Thanks a lot for this work. This makes using windows a lot easier. :-)
Hello,
Together with the automatic builds this brings automatic updates
for every new release built for windows.
does still all packages get build automatically?
E.g. the latest releases here are not build:
http://pecl.php.net/package/amqp
But yaf is getting build: http://pecl.php.net/package/yaf
Maybe for amqp there is just a build error?
Hi Martin,
Hello,
Together with the automatic builds this brings automatic updates
for every new release built for windows.does still all packages get build automatically? E.g. the latest releases
here are not build: http://pecl.php.net/package/amqpBut yaf is getting build: http://pecl.php.net/package/yaf
Maybe for amqp there is just a build error?
Yes, that's exactly the issue, you can check the logs under
http://windows.php.net/downloads/pecl/releases/amqp/ .
Rephrasing my old mail, every package released on PECL is passed through
the build system. Still every single build isn't monitored manually, so if
there was some errors and nobody pings, it might just stay on ice.
So thanks for the ping. Actually I'd call anyone interested to not to
hesitate - ping on errors so they get resolved faster. Also, snapshots can
be done manually before release to check everything is fine, please ping
as well for that.
Regards
Anatol
Hello Anatol,
So thanks for the ping. Actually I'd call anyone interested to not to
hesitate - ping on errors so they get resolved faster. Also, snapshots can
be done manually before release to check everything is fine, please ping
as well for that.
Found a package which seems to be build fine, but there is no download like:
http://windows.php.net/downloads/pecl/snaps/redis/2.2.5/
http://pecl.php.net/package/redis
Best regards
Martin
Hi Martin,
Hello Anatol,
So thanks for the ping. Actually I'd call anyone interested to not to
hesitate - ping on errors so they get resolved faster. Also, snapshots
can be done manually before release to check everything is fine, please
ping as well for that.Found a package which seems to be build fine, but there is no download
like:
http://windows.php.net/downloads/pecl/snaps/redis/2.2.5/
http://pecl.php.net/package/redis
there was some fixes AFAIR merged since then. Still no new releases
uploaded to PECL.
But if you compare the release dates, the package on PECL was released in
March 2014, whereby the snap is from July. That's because the builds
descend to the patches which wasn't applied by that time, aka from a
forked branch. That of course can't be called a release build, so it
should go into snaps.
Despite I see new releases https://github.com/phpredis/phpredis/releases ,
none is uploaded to PECL and consequently nothing is built.
Regards
Anatol