Am 09.03.2017 um 20:00 schrieb dick balaska:
> Am 2017-03-09 09:08, also sprach clipka:
>> Am 09.03.2017 um 09:26 schrieb dick balaska:
>>> Am 2017-03-08 08:28, also sprach clipka:
>>>> Am 08.03.2017 um 00:15 schrieb dick balaska:
>>>>
>>>>> Ah bollocks.
> 
>>>>
>>>>     %ProgramFiles(x86)%\Windows Kits\10\Include\10.0.10586.0
>>>>
>>>
>>> I don't see anything that says "Windows XP Support for C++".
>>> I don't have that 10.0.10586.0 directory.
>>
>> Do you have a `10.0.10240.0` directory instead?
> 
> Yes. 10150, 10240, and 14393.

Dang!
Looks like there's an even newer Windows SDK out by now which /I/ don't
have installed.

In the installer, can you check whether you see the following features:

    ...
    [ ] Windows and Web Development
      ...
      [ ] Universal Windows App Development Tools
        [ ] Tools (1.4.1) and Windows 10 SDK (10.0.14393) <-- (1)
        [ ] Emulator for Winodws 10 Mobile (10.0.14393)
        [ ] Windows 10 SDK (10.0.10586)                   <-- (2)
        [ ] Windows 10 SDK (10.0.10240)
      ...

I suspect you may have (1) checked (which I don't; no need to uncheck it
though), but have (2) unchecked (same here so I probably have that SDK
from some other source).

Please try whether checking (2) magically brings you the directory named
above.


> I meant that the installation wasn't totally broken.  I freaked a little
> when basic system files like stddef.h, stdlib.h, and sys/types.h were
> missing.
> 
> I imagine it's trying to select different versions of those? Possibly
> the "XP Compatible" versions?

Yup.
More precisely, the versions from the 10.0.10586 SDK, which we know to
be good (as opposed to the 10.0.10240 SDK, which we know to be bad).

Unfortunately, hard-coding the SDK version into the project files means
that even a later SDK won't do. Accept no substitutes!

Post a reply to this message