clipka <ano### [at] anonymousorg> wrote:
> Which leaves the question why we can't build nice working binaries on
> GitHub using the v142 (VS 2019) toolset.
I know nothing about it, but since not sure some stuff is not modified from your
initial settings when opening and converting toolset, let me just copy
(translate from french) some stuff that's in bold in my setup, in case it would
Windows SDK version is 10.0
The C++ iso norm is c++14
The C version is MSVC project inherited.
MFC is set to use Standard Windows Library
Floating point model is on Precise (/fp:precise)
Activate type informations at run time (/GR) : set to yes
Whole code optimized for speed (/Ox)(/GL)(/Ot)
Security check is deactivated (/GS-)
Improved instruction set "undefined"
Startup banner removal set to yes (/nologo)
Forcing for loop scope conformity set on (/Zc:forScope)
Preprocessor definitions :
Expand inline function set to Whenever possible (/Ob2)
Function level linking deactivated (/Gy-)
Precompiled header, set to be in use (/Yu)
Precompiled header file set to winprecomp.h
Output precompiled header file set to $(IntDir)winprecomp.pch
Disable specific warnings set on with 4800;%(DisableSpecificWarnings)
Forced Include files set to winprecomp.h;%(ForcedIncludeFiles)
Warning level is 3 /WX- (do not consider warnings as errors)
Anything else you want me to check ?
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 it be that some libraries had relative paths and then the Github system
not having the same reference point for relative paths ?
Maybe you could try submitting a totally different branch (such as HGpovray38 or
povr, to find out if the feedback is more verbose or the issue similar? )
Post a reply to this message