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.

>
>> "Tools -> Extensions and Updates" shows what I have installed. Not any
>> new things I may want.
>> I started up the installer hoping there was an "XP blah" setting in
>> that, no.
>
> You do have VS 2015 Update 3 now, right?

Microsoft Visual Studio Community 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01055

>
> In the installer / "modify-my-installation" thing, you should see the
> following tree in the "Features" category:
>
>     [#] Programming Languages
>       [#] Visual C++
>         [*] Common Tools for Visual C++ 2015
>         [ ] Microsoft Foundation Classes for C++
>         [*] Windows XP Support for C++            <--- This!
>       [ ] Visual F#
>       [ ] Python Tools for Visual Studio (January 2017) (New)
>     [ ] ...
>

Yes, I have that. (Also MFC classes is checked). Sorry, I didn't see the 
additional dark-grey-on-black tree selector last night.

If I uncheck XP Support, the Next button becomes available and it offers 
to remove XP Support.

>> The installation is ok.  I can build previous versions of povray, like
>> this 2017-02-12 version I had laying around that calls itself
>> 3.7.2-alpha.unofficial+msvc14.win32
>
> The fact that you can build earlier versions of POV-Ray doesn't
> necessarily indicate that the installation is ok. It only means that the
> /XP-incompatible/ portions of the installations are ok. Your builds of
> those earlier versions will /not/ run on XP.

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?

>
> Those earlier versions only built "out of the box" on your VS 2015
> installation because our VS (2010) solution was set up to build
> XP-incompatible binaries if auto-converted to VS 2015.
>
>
>> This is VS2015 Community Edition.
>
> Same here.
>


-- 
dik

Post a reply to this message