clipka <ano### [at] anonymousorg> wrote:
> Am 20.06.2021 um 12:29 schrieb Mr:
> > I'll close and re-popen the project and try harder to spot any information at
> > the step when I pick platform toolset v142.
> Could you have VS 2019 auto-convert the projects to toolset v142, save
> the resulting projects, and post some of them over on
> `povray.vcxproj` and `povbase.vcxproj` should be helpful. Maybe also
> > Could it be that some libraries had relative paths and then the Github system
> > not having the same reference point for relative paths ?
> No, I don't think that's it. My money is on some project setting that
> needs to be changed along with the toolset, that we don't account for.
Also take into consideration that I made all the updates that were suggested by
VS at its startup and there were a couple along the past year. Even right now
there is one pending saying version 16.10.2 is now available that I was about to
I just attached to this reply the requested files since I don't see
povray.beta.test.binaries in the http interface to newsgroups.
I added a couple of files that had similar names but different suffixes.
I never actually saved the files but when I made the conversion the first time
it seems to have done so and remembered the toolset, never asking me again if I
wanted to convert files made from an older version.
Don't hesitate to ask whatever else may be needed, and to my private email also
if you feel it's irrelevant to newsgroups... though most of the times such a
public searchable record can be nice for ulterior use.
Post a reply to this message
Download 'vs2015_but_2019_really.7z.zip' (9 KB)