POV-Ray : Newsgroups : povray.beta-test : Visual Studio 2017 or 2019 : Re: Visual Studio 2017 or 2019 Server Time
20 Sep 2021 12:56:55 EDT (-0400)
  Re: Visual Studio 2017 or 2019  
From: Mr
Date: 19 Jun 2021 15:30:00
Message: <web.60ce44a55784b3396adeaecb3f378f2@news.povray.org>
clipka <ano### [at] anonymousorg> wrote:
> Am 19.06.2021 um 16:25 schrieb Mr:
>
> >> does anyone happen to have VS 2017 and/or VS 2019 installed, and can try
> >> to compile POV-Ray with "Platform Toolset" changed from `v140` to `v141`
> >> or `v142`?
> >>
> >> I'd be interested to hear about your experience: Whether POV-Ray does
> >> compile - whether it runs as expected - and if not, what might prevent
> >> it from doing so.
> > Hello. In Visual Studio 2019, windows 10:
> > *Downloaded this :
> > https://github.com/POV-Ray/povray/archive/refs/heads/master.zip
> >
> > *unzipped and opened this  ...\povray-master\windows\vs2015\povray.sln with
> > option to auto update project toolset to v142
> >
> > *Choosing "Debug" ; and "x64" in the top bar solution config rolldowns.
> >
> > *changing     #define BUILT_BY "YOUR NAME (YOUR EMAIL)" line 128
> > and removing  #error line 129 right below it of
> > .....\povray-master\source\base\build.h
> >
> > *picking GUI in Windows tagrets and top menu Generate > Generate Solution
> >
> > * Waited a while and properly got pvengine64d.exe inside
> > .....\povray-master\windows\vs2015\bin64
> > Output message (originally in french)ended by :
> > ========== Cleanup : 21 succeeded, 0 failed, 2 were ignored ==========
> >
> > * Done a Generate > Cleanup solution and picked Release option before trying
> > that right now!  My computer is an I7 Q720, so should I try Release-AVX or
> > Release-SSE2 after that ?
>
> Thanks for helping dig into this.
>
> To be honest, I did expect it to compile. The big question is: Do the
> binaries actually do anything when you run them?
>
> Mainly interested in the "pure" Debug and Release builds.
>
>
> If they seem to work fine, please do me a favor and try again with
> `#define POVRAY_IS_BETA` enabled and `#define POV_RAY_HOST_VERSION ...`
> commented out in `source/base/version.h`.
>
> I'd also be interested to learn what "auto update project toolset" does
> to the project files, besides changing the toolset from `v140` to `v142`.

Both Debug and Release do render simple scene with radiosity, point
lamp,recursive AA, mesh2 cube, 1000 sphere_sweep union, over global single
scattering media using "version 3.7" statement.
Now trying your suggested changes, assuming both at once right?


Post a reply to this message

Copyright 2003-2021 Persistence of Vision Raytracer Pty. Ltd.