Newsgroups: php.internals,php.internals.win,php.windows
Path: news.php.net
Xref: news.php.net php.internals:96677 php.internals.win:1152 php.windows:31427
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error)
To: "'PHP internals list'" <internals@lists.php.net>,
	"'internals-win'" <internals-win@lists.php.net>,
	<php-windows@lists.php.net>
Date: Mon, 31 Oct 2016 18:01:36 +0100
Message-ID: <012201d23398$72f2dc50$58d894f0$@belski.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AdIyGeNwroBlHRIgQZyfQpwdfAzzdA==
Content-Language: en-us
Subject: New PHP SDK for Windows
From: anatol.php@belski.net ("Anatol Belski")

Hi,

I'm working on the new Windows PHP SDK. So far, some usable alpha state is
reached. It is compatible with PHP-7.0 and the current SDK and contains
additional new features. The essential changes in the new SDK are

- starter scripts included, making the environment setup easier
- updated tools, including bison 3.0.2
- more tools including sed, awk and others based on MSYS2
- new tool for dependency update automation

The current state is reachable under

https://github.com/OSTC/php-sdk-binary-tools/tree/new_binary_tools

I would like to call everyone interested to please check and provide
feedback and PRs. Other useful tools can be invented on the base of the new
SDK. Production usage is not yet recommended, but the more feedback is there
- the closer it'll be. The plan is to replace the current PHP SDK with the
new one in foreseable future for PHP 7 builds, maybe also to backport for
the 5.x tree. This also correlates with the upcoming AppVeyor integration,
and both tasks in general are directed to improve the QA and experience
situation when building PHP on Windows.

Please check more on the github README page. If some tool is missing or is
worth it to be implemented, please create a ticket. A new step-by-step-build
wiki page will also need to be created, once the new SDK was considered
stable. I would also ask to migrate the linked repository to git.php.net,
meanwhile the PR can be accepted on the OSTC repository page.

Thanks

Anatol