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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
