Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95953
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
To: internals@lists.php.net
References: <616bb9ff-bcd1-fd70-b251-05b280b5003e@lsces.co.uk>
 <CANUQDCh=xC5G2FS2a-jm3aKATwV1BuOhd+AQiCq7tnMUvruFcA@mail.gmail.com>
 <fc0df908-0e9d-e748-70cb-9d9a6e8d4ee6@lsces.co.uk>
 <CAH-PCH5FadFFygmXQE35Fzr6sDniG8rdsnVvWA9FYE+404RYog@mail.gmail.com>
 <e441c74d-7c4a-393a-fa05-21b9f80fd214@lsces.co.uk>
 <CAH-PCH6vE4EV0YaX-q_USUdH1KcsemMhbvN=e9iKqCpEPnrHfw@mail.gmail.com>
 <52ae5494-f466-ac4d-c166-d47752b13344@lsces.co.uk>
 <32c3a330-cdfa-f310-85d7-d01eacbf3b86@lsces.co.uk>
 <ea77902b-c5c2-2f6c-0091-99a10b91a634@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>
 <acaf07f1-c7b6-c25d-12a0-9a3e29835d9c@gmx.de>
Message-ID: <747074aa-034d-5f86-4b2c-a0b1e48579c8@lsces.co.uk>
Date: Mon, 12 Sep 2016 21:06:31 +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: <acaf07f1-c7b6-c25d-12a0-9a3e29835d9c@gmx.de>
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 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.

>>> 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?

>>> 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. :-)

I seem to be making some progress finally on starting switching
production machines to PHP7.

-- 
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