On 11/09/16 11:05, Christoph M. Becker wrote: > On 10.09.2016 at 23:45, Lester Caine wrote: > >> On 10/09/16 16:41, Christoph M. Becker wrote: >> >>> Despite the rather common myth, building PHP on Windows nowadays is not >>> really harder than on Linux. Detailed instructions are available on >>> <https://wiki.php.net/internals/windows/stepbystepbuild>. >> >> http://lsces.co.uk/wiki/Compile+PHP7+Build+on+Windows+10 > > Wrt. concrete build problems, I suggest asking on an appropriate mailing > list or support forum, such as php-wind...@lists.php.net.
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'. I'd actually managed to pick up the wrong link because of the ARM tools install. It's also confusing if one has come from a Linux base and are used to a command prompt just working :) I will pad that out on my wiki page ... when time permits. >> But while the licensing is fairly loose for individual developers, I >> doubt that any government IT department could get passed the >> 'enterprise' restrictions on use ... which was the block on earlier >> options for building windows versions as well. > > 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. > 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. This latest one is the first since 2011 :( I can see a way to package 'composer' to provide a centrally available tool, but it will take some time to work out how to dovetail it into the other package management systems. Looking to 'update' to composer when I'm also trying to update a working javascript set-up is part of the current hold up on completing an improved form validation upgrade ... do I need either package handlers? Not currently since everything is under DVCS already. -- 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
