Hi,

the work was done for extension windows builds to be done automatically.
The base is the windows snapshot build system and the work is still

in progress. At the moment we have a system, which can be triggered
manually and builds a PECL package automatically for every supported PHP

version, then uploads the binaries and/or build logs to
http://windows.php.net/downloads/pecl into the corresponding subdir.

Here are some examples of the automatic builds
http://windows.php.net/downloads/pecl/releases/rar/3.0.1/
http://windows.php.net/downloads/pecl/releases/pthreads/0.0.45/
http://windows.php.net/downloads/pecl/releases/automap/2.1.0/

Currently the following is needed for an extension to be successfully built

- only PECL packages are supported right now
- add config.w32 to the package.xml
- ensure config.w32 is correct
- ensure the extension name in the package.xml and config.w32 is the same,
as well the folder name in the tgz for instance mypackage-1.0.0
- ensure you have the correct version in package.xml
- ensure you have the correct lead email in the package.xml (for the build
alerts)
- ensure there are no mails in the CREDITS file as that'll break the build

The PECL integration is to come up. Automatic windows builds to be
activated in the PECL dev accounts, on demand or per release, are planned.

In some far perspective also phpize instead of full build (minimize build
log, enable extension deps), building from source, building from a

revision, static analyze enabled, PGO, make test ...

For now, if one is interested on building a package please ping me. But
please check with the list above

before. The extensions without deps can be done easy. The exts with
library deps need those to be prepared before, of course.

Best regards

Anatol

-- 
PECL development discussion Mailing List (http://pecl.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to