Re: [INTERNALS-WIN] PHP7: which Windows Kit?
[email protected] (Jan Ehrhardt) Tue, 04 Aug 2015 21:21:32 +0200
| Newsgroups | php.internals.win |
|---|---|
| Message-ID | <[email protected]> |
Hi Anatol, "Anatol Belski" in php.internals.win (Tue, 4 Aug 2015 10:16:58 +0200): >Your information is not correct. A separate SDK is only needed when an >earlier VS version is used. And SDK 10 needed when targeting specific Win10 >features. PHP7 only requires UCRT which is present on Win10/Server 2016 by >default or available as a VC++ redistributable on lower. This discussion suffers from talking about semantics like targetting and the use of SDK's. Let us just talk filenames. I installed VS2015 Pro and chose to install the Windows 10 UM as well. If I follow the wiki description, open up a 'Developer Command Prompt for VS2015' to compile PHP7 or Openssl, the building process includes C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\um\WinSock2.h The people from Apachelounge also installed VS2015 but chose not to install the Windows 10 UM. If they follow the wiki description and open a 'Developer Command Prompt for VS2015' the build includes C:\Program Files (x86)\Windows Kits\8.1\include\um\WinSock2.h If you say that should not make any difference, I will take your word for that. But I have my doubts. >Regarding headers - within same VS version ABI/API compatibility is usually >kept. Those files in C:\Program Files (x86)\Windows Kits\8.1\include\um\ were installed together with VS2013 and the ones in C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\um with VS2015. Is that the "same VS version ABI/API"? -- Jan