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.
>>
>> Do you have the "Windows XP Support for C++" component of VS 2015
>> installed? I'm sure our project files need it, and although I never
>> tested what /exactly/ happens when it's missing, the symptoms appear to
>> be at least in the right ballpark to potentially fit that bill.
>>
>> Alternatively something might have gone wrong with the installation of
>> the updated Windows C++ runtime library. Check to see whether you have
>> the following directory on your machine:
>>
>>     %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?

> "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?

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)
    [ ] ...

> 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.

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.

Post a reply to this message