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.beta-test.binaries`?
>
> `povray.vcxproj` and `povbase.vcxproj` should be helpful. Maybe also
> `povray.sln`.
>
> > 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.

Hi, since then, I tried compiling for some machine that had never been exposed
to POV and got the same error message ("Cannot find Home entry in registry"):
This is to be expected when I did not do the pre requisite step of installing
any version from any previous official installer first.

However this was on purpose, as I had hoped to ultimately operate the build and
missing details of its installation process from some other package build. So
having to install a pre built package prior to build the provided sources would
not be a possible hack.


Thus my question now is... Is there any Windows geared alternative procedure
where one can build pov from some readme, AND use it, even if it has never been
installed? Is it likely that the unix prebuild.sh / make install steps are not
yet mimicked under Windows but might be with the help of the git sh tool ?
(sorry if this last point makes no sense I'm trying guesses in the dark.)

Post a reply to this message