TypeInfo.lib build failure with post-hiatus source

[grayman]

I updated my darkmod and darkmod_src repos this morning, and the first attempt at building a 64-bit Windows binary ran into the following error:

 

2>   Creating library E:\Trunk\darkmod_src\..\darkmod\TypeInfo.lib and object E:\Trunk\darkmod_src\..\darkmod\TypeInfo.exp
2>idLib.lib(Simd_SSE2.obj) : error LNK2001: unresolved external symbol "class idCVarBool r_legacyTangents" (?r_legacyTangents@@3VidCVarBool@@A)
2>E:\Trunk\darkmod_src\..\darkmod\TypeInfo.exe : fatal error LNK1120: 1 unresolved externals
2>Done building project "typeinfo.vcxproj" -- FAILED.

 

Can anyone who's been working in this area please fix this?

Thanks!

[grayman]

I can't read the code block in my previous post, so here it is without the blocking:

 

2>   Creating library E:\Trunk\darkmod_src\..\darkmod\TypeInfo.lib and object E:\Trunk\darkmod_src\..\darkmod\TypeInfo.exp
2>idLib.lib(Simd_SSE2.obj) : error LNK2001: unresolved external symbol "class idCVarBool r_legacyTangents" (?r_legacyTangents@@3VidCVarBool@@A)
2>E:\Trunk\darkmod_src\..\darkmod\TypeInfo.exe : fatal error LNK1120: 1 unresolved externals
2>Done building project "typeinfo.vcxproj" -- FAILED.
 

[grayman]

Aaaaannnd ...

While the 64-bit binary TheDarkModx64.exe builds after this morning's update, it crashes when attempting a dmap.

Who needs what to debug this?

[grayman]

Also getting this failure on the 32-bit build:

 

1>idlib.vcxproj -> E:\Trunk\darkmod_src\\build\Win32\Release\idLib.lib
2>------ Build started: Project: TypeInfo, Configuration: Release Win32 ------
2>Error: The operation could not be completed. Unspecified error 
 

[stgatilov]

You can unload TypeInfo project, it is only needed for the weird "Memory Log" configuration.

As for linking error, I guess Duzenko should fix it. Meanwhile, you can comment everything related to r_legacyTangents, and it would work.

[grayman]

Removing TypeInfo removes the compilation error.

A source search for r_legacyTangents finds nothing, so I can't follow this suggestion.

Now, a fresh complete build of the binaries yields binaries that don't even get to the point where they display anything on the screen. A check of running applications shows no TDM.

If someone could try a build of the latest binaries and show they create working exes, it would be appreciated. Then I can begin to narrow down what's going on at my end. If no one else can get the SVN binaries to run, then whoever's been making the latest source changes needs to review their work. SVN binaries should always run.