Newsgroups: php.internals,php.internals.win,php.windows Path: news.php.net Xref: news.php.net php.internals:96922 php.internals.win:1153 php.windows:31430 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41041 invoked from network); 16 Nov 2016 14:43:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Nov 2016 14:43:37 -0000 Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.22 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.17.22 mout.gmx.net Received: from [212.227.17.22] ([212.227.17.22:49762] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C2/80-05303-3907C285 for ; Wed, 16 Nov 2016 09:43:32 -0500 Received: from [192.168.1.190] ([79.243.119.150]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MWkZL-1cIjps1C9b-00Xvzy; Wed, 16 Nov 2016 15:43:27 +0100 To: Anatol Belski , 'PHP internals list' , 'internals-win' , php-windows@lists.php.net References: <012201d23398$72f2dc50$58d894f0$@belski.net> Message-ID: <0eac9e76-8bee-45b7-a87c-fc84524e01f9@gmx.de> Date: Wed, 16 Nov 2016 15:43:40 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <012201d23398$72f2dc50$58d894f0$@belski.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:a/kYPnfRsJ7QUrRRee/gk4TvL8lAoCWItkDnLb0aJWYa7fpbNkw quGPHaFUfa2BSRp9NNJySbGZGRLVmb1VYfYTtfI75tSMbaUUM4b1Sa7/a8SqW5+sNnb1eSs 2QKbMUouJ5cxCK2wHGIajaSk80+xa+7QJbPiQ31g4J/xBwRz3fCo3lQR1D53KF4aHfkwRzB RCdw0Rm4bfcGQ2cp4q8PQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:k5hx2nCIX1Q=:ylrfGruZMcqzJxCtE+Uxv3 PjSo5GYoC2Ly1u8mwg1WZsINWcc6VZdnx/eAun9HwH/KYyf9oYjti7w6utyVwY9KsBP6h6ts5 1Y7qCZzX2YdChQpXAUazJc5gBICR+rZ9+4+vXJQ/JSP1Yb5Ny3U50a5i7xj2Nov0n3in1eB45 jisQctpymnh4sDUbUBk8VIluUVNUigomB6NtDSK0cqygX6M1v/Kzk/FzC1D+RutR35nfW/wTf jBuN3RFsJaJjj6w6aLxvapnSCseZv7jfGFi5tmajylh3ViCRZgXALd1o0c5wipjmTQJQSo3hM AIOldK9yIQN0rRX1CJr6yZp7uyoESEXSKU6Z5I9zQYi3v9a6OVTgeD4vdphomXaTolNWc5Wsc tVRdp/G1bJ3NQU0PHOISBDNUw3zNl65SRsYbhXYwcZ1ugoNJXNTcEXX3EQw1D49nmnLjVLoNo EbsXYX0yl3oYd56JFyxN7nlMOxD5UTvTAAAYfWqDPMw0H2ZLyHmoD/nSQFYjf13g1WlVjLtmu 2+XivrWv4Mk3w8TTr9Et4+Yycqnw5zLeTg74F3azsgtvRU31X0w4YoyYzwYQOh3M0yIpv6qH7 jrMTtpQbV9bOALd56j6GPcPJyB9Ttkj8qdZ1Gl9CEJX9eyWZ+fIZ2vzCmtWOxzFGKSvnghF6i w3G2ixXUlnNFky+nXgzWQ25qaeIiTIU9irAv6xyBHhRI6hj1ZwjsvInPVbmPFMIch3VdtVl60 0vaRGd7l8Tv9PPiGMyrtaFObwOVJtcw1ki2qh7RgSpH1dmfWkWAkcuT2X1vZNeCN0DyoTtuS+ L0cJSSI Subject: Re: New PHP SDK for Windows From: cmbecker69@gmx.de ("Christoph M. Becker") Hi Anatol! On 31.10.2016 at 18:01, Anatol Belski wrote: > 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. I still hadn't had the time to have a closer look at the new SDK, but finally managed to at least quickly check it out – it looks very promising. Thanks for the good work again, Anatol! -- Christoph M. Becker