Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95952 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45595 invoked from network); 12 Sep 2016 19:31:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2016 19:31:31 -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.15.18 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.15.18 mout.gmx.net Received: from [212.227.15.18] ([212.227.15.18:49545] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C4/00-45240-19207D75 for ; Mon, 12 Sep 2016 15:31:30 -0400 Received: from [192.168.2.103] ([79.243.115.246]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MXZbS-1bUnvf17ME-00WS73; Mon, 12 Sep 2016 21:31:25 +0200 To: Lester Caine , internals@lists.php.net References: <616bb9ff-bcd1-fd70-b251-05b280b5003e@lsces.co.uk> <52ae5494-f466-ac4d-c166-d47752b13344@lsces.co.uk> <32c3a330-cdfa-f310-85d7-d01eacbf3b86@lsces.co.uk> <8e659a83-7abd-0ab1-0085-c8b8a073d929@gmx.de> <254a8191-f527-7d88-f1c1-25df76528ef8@lsces.co.uk> <628696aa-0aed-a145-c248-84abb1262878@gmx.de> <166ce0a2-70e7-741e-5baa-7577d1d51c47@lsces.co.uk> Message-ID: Date: Mon, 12 Sep 2016 21:31:36 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <166ce0a2-70e7-741e-5baa-7577d1d51c47@lsces.co.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:wLxTvdHE/JlVmu7yvxaeAidg2eQEtaJSvWIGNyIyRrFNNKZKTFR lpRbDbT07fQOBqD1O3s29EGD+1U7L/NcIkHdF4jBijPtgPYlVU858J5zQ3xxVAeD7A3hqqi 6WKGrUmowfTpW5CS1u+0YXByoKxQN05x5U+EgQV7BrL+QP/W7jssM3p/EvwpmXYxo4GWUHt 3OYHfohCIe8BBHysaEm9A== X-UI-Out-Filterresults: notjunk:1;V01:K0:frX62SMMOBU=:On7SvrfmzOcNkXSkz12Ssj ApypzShy5VfeIkjmjoY9DW5oeuT5AJ8gyjAMMlm9Y0KuqT14SkHsO8WBYVtWPWdk/wbtThn4O 2fZeHFELTIv344vllebIzwIam6k72tBDFpW+reL8aQYPq8aif6JHmmcCBXOwi845lVLL+ssGl FgfGUdv+h5wopaFJ8pJ3C3xCp2ylFfPZU+sfnu1i32be1QGnujAYq8azBtM5YT53NdAkYhqgB GI/qa3RVoKJut5CO9O7rgHaUAHBLhCvMhUH3Va5t5/IPnfl2j712LsWScLEuozFvo1SysOSJW uRKjGsJEMRiyNfJHzHBv2z2urRIyBkNGrg4T3GGyUQ9gMaxUL3REnJkelw77j9AzcA80RaKQq 65mvAtjOrYzfbkUKcMP2wVNbk9unuuoaSmgSqZdTjgXJi4iKe/Hs+MTqfLGoVI6SSboGnEQkl R/VjHlP+stjtc239IqrSZiKLFOHr4sipTDNzE/piGOBhQa+GDTS0kYrOxjd0DroINnEfIySAQ TuOAniNBVB+4rhnaC4+L4s1no400Ug1msN/PtkJ+X1IFp9xdWKx0CtUrX4wb0sB6UDNGm2l85 rD0Etb/knDkV6gCMd71y50KE0YscHZVv0+EO4y/KtQgH7LWWr4hTU45a/gkti7V2AOsnyT0H5 ASStC4n1r1ju+KipPWQ3XanFtf4dpEFUK+oRGd4n3PEMy15M2HVrf8vZRUAOq7ItLVUItIlBw vERGQwE+/P9ATGJQaPbT+1kY4tU8adzmZ5oqLwhwyDGVo4GMAVjIwkf6NJy+/XYgPCilCabPp ZAtzhB2 Subject: Re: [PHP-DEV] Modern practices ... From: cmbecker69@gmx.de ("Christoph M. Becker") On 11.09.2016 at 12:35, Lester Caine wrote: > On 11/09/16 11:05, Christoph M. Becker wrote: > I have already debugged the problems and will tidy up the notes later > when I cross check things. This is the sort of support I've always > provided to the PHP project. The pages relating to the compile process > on the php wiki need bringing up to date but I don't think I have access > to do that with my wiki login. One key element which a newcomer may miss > is the 'command prompt' needs to be the special command prompt VS15 > generates rather than 'just a command prompt'. Hm, the Wiki page states: | If compiling PHP 7.0+ open either the “VS2015 x64 Native Tools | Command Prompt” or the “VS2015 x86 Native Tools Command Prompt”. >> The licensing of Visual Studio doesn't appear to be a PHP issue. > > Only if the 'official' installation path requires use of software that > has restricted licensing. While there are binary builds for windows > there is not a problem, but if a replacement pecl path required the use > of Microsoft tools the licensing does become a problem. I don't see why a replacement for pecl would have other licensing issues as pecl. >> Support for other toolchains may be added; patches are welcome! :-) > > Again something I have tried to maintain in the past, but the volume of > work on the TODO list is delaying bringing many of the old crib sheets > up to date. I guess, we all have more on our TODO list than we can actually manage. :-) -- Christoph M. Becker