Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95978 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22174 invoked from network); 13 Sep 2016 08:47:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Sep 2016 08:47:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:58933] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FE/5A-60695-40DB7D75 for ; Tue, 13 Sep 2016 04:47:01 -0400 Received: (qmail 21315 invoked by uid 89); 13 Sep 2016 08:46:58 -0000 Received: by simscan 1.3.1 ppid: 21309, pid: 21312, t: 0.1084s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 13 Sep 2016 08:46:58 -0000 To: PHP internals 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> <747074aa-034d-5f86-4b2c-a0b1e48579c8@lsces.co.uk> Message-ID: Date: Tue, 13 Sep 2016 09:46:57 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Modern practices ... From: lester@lsces.co.uk (Lester Caine) On 13/09/16 01:44, Pierre Joye wrote: > On Tue, Sep 13, 2016 at 3:06 AM, Lester Caine wrote: >> On 12/09/16 20:31, Christoph M. Becker wrote: >>> 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”. >> >> As it's a couple of levels deep the prompt in my crib sheet was to how >> to find them, but a little explanation on why you need to use a special >> command line prompt for people who ARE coming from a click and go >> environment will be helpful. > > Simply because php does not generate solution project files. It is > nearly impossible to support all version, while recent VS tends to > change less from one version to another. Pierre ... I have no problem here ... I'm simply trying to do what I did 15 years ago when I first created crib sheets to help ME work out how to make things happen. Often things that are obvious to someone who has grown up with a system need a different perspective when helping others get up to speed. >>>>> 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. >> >> It's the same problem as has always existed with the free tools only >> being licensed for non-commercial use. As long as binary files are >> available there is not a problem, but the fine detail of licences seems >> to change with every new release? > > This statement is wrong. Please check the VS/VC license, the free one. > Commercial usage is just fine. Off topic I know, but can you provide a link. I need to update a couple of audit documents which include getting PHP7 listed with the options for on-going support. People do like to push the high priced commercial alternatives claiming open source is not really free :( > Also a large majority of users do not need it, neither they need > gcc/icc as they will simply used the respective binaries. > > That being said, on windows we do provide PGO builds, which bring a > significant performance gain. It is possible to do it yourself too but > I am not sure why one would go through that :) Anything that helps education! And certainly I am still seeing windows stacks a lot slower than on Linux on the same hardware. What is the right way to do a windows install? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk