Newsgroups: php.internals,php.internals.win,php.windows Path: news.php.net Xref: news.php.net php.internals:98216 php.internals.win:1164 php.windows:31442 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60800 invoked from network); 6 Feb 2017 16:33:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Feb 2017 16:33:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:44878] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2A/05-30708-455A8985 for ; Mon, 06 Feb 2017 11:33:25 -0500 Received: by h1123647.serverkompetenz.net (Postfix, from userid 1006) id 78247784B7A; Mon, 6 Feb 2017 17:33:21 +0100 (CET) Received: from w530phpdev (p54A77588.dip0.t-ipconnect.de [84.167.117.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by h1123647.serverkompetenz.net (Postfix) with ESMTPSA id 45C25784A76; Mon, 6 Feb 2017 17:33:19 +0100 (CET) To: "'PHP internals list'" , "'internals-win'" , References: <012201d23398$72f2dc50$58d894f0$@belski.net> In-Reply-To: <012201d23398$72f2dc50$58d894f0$@belski.net> Date: Mon, 6 Feb 2017 17:33:14 +0100 Message-ID: <029401d28096$b991de40$2cb59ac0$@belski.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQKaxd5WrHC4z+b0o0CHGLrdDCZabZ/LmALg Content-Language: en-us Subject: RE: [PHP-WIN] New PHP SDK for Windows From: anatol.php@belski.net ("Anatol Belski") Hi, > -----Original Message----- > From: Anatol Belski [mailto:anatol.php@belski.net] > Sent: Monday, October 31, 2016 6:02 PM > To: 'PHP internals list' ; 'internals-win' win@lists.php.net>; php-windows@lists.php.net > Subject: [PHP-WIN] New PHP SDK for Windows > > 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. > So far the point was reached, so then the current new binary tools SDK implementation is close to stable. For about two months already, all the AppVeyor builds use the new SDK, the current master snapshots use it as well. Many people reported good experiences with it, some bugs were fixed and more improvements was made. At this point, I've also started to adapt the documentation https://wiki.php.net/internals/windows/stepbystepbuild_sdk_2 and the actual plan for the next 2-3 weeks is - move the further development into the master of php-sdk-binary-tools - if someone from systems has time, still please add this repo to git.php.net - do a stable release of the binary tools 2.0.0 - make PHP 7.2 to require the new binary tools and solve https://github.com/OSTC/php-sdk-binary-tools/issues/1 I'd appreciate any help with the wiki doc page. Some quite exhaustive information is also available on the SDK's own readme page in the git repo, which might make less sense to be duplicated on the wiki. Still, I could miss something, so any review is useful. Any further tests on the SDK itself were ofc welcome, too. Regards Anatol