Trouble compiling T3D (Release mode) LNK2019
by John-E · in Technical Issues · 10/20/2015 (2:21 pm) · 8 replies
Hello everyone,
A new T3D user here and I must say that it's a pretty amazing piece of software. But getting to the point:
Compiling the engine on VS 2015/Windows 10.
-Debug mode: All's nice and cool!
-Release mode: Error LNK2019
unresolved external symbol __vsnprintf referenced in function "long __stdcall StringVPrintfWorkerA(char *,unsigned int,unsigned int *,char const *,char *)" blah blah blah blah blah buildFilesVisualStudio 2015projectsDxErr.lib(dxerra.obj)
Seems like the project DLL is in trouble. Any ideas?
Also why don't we get a project dll when the project generation is done using the project manager?
A new T3D user here and I must say that it's a pretty amazing piece of software. But getting to the point:
Compiling the engine on VS 2015/Windows 10.
-Debug mode: All's nice and cool!
-Release mode: Error LNK2019
unresolved external symbol __vsnprintf referenced in function "long __stdcall StringVPrintfWorkerA(char *,unsigned int,unsigned int *,char const *,char *)" blah blah blah blah blah buildFilesVisualStudio 2015projectsDxErr.lib(dxerra.obj)
Seems like the project DLL is in trouble. Any ideas?
Also why don't we get a project dll when the project generation is done using the project manager?
#2
Thanks for the fast reply!
I haven't used the project manager for this one. I'm not font of magic buttons especially when learning new stuff. I decided to follow this guide instead: http://wiki.torque3d.org/introduction:creating-a-project-without-the-project-manager. Maybe a bad idea for a T3D beginner? I noticed that using project manager wont produce any dlls at all.
I named the project "Test01". Debug mode generates "Tes01_DEBUG.exe" and "Test01_DEBUG.dll" and it works fine. The problem comes when I switch to release mode. Compiling "test01.dll" pops up that LNK2019 error.
Also my apologies if I'm using the wrong forum. Should I move my question to the forum you linked?
10/20/2015 (2:54 pm)
Hi Steve,Thanks for the fast reply!
I haven't used the project manager for this one. I'm not font of magic buttons especially when learning new stuff. I decided to follow this guide instead: http://wiki.torque3d.org/introduction:creating-a-project-without-the-project-manager. Maybe a bad idea for a T3D beginner? I noticed that using project manager wont produce any dlls at all.
I named the project "Test01". Debug mode generates "Tes01_DEBUG.exe" and "Test01_DEBUG.dll" and it works fine. The problem comes when I switch to release mode. Compiling "test01.dll" pops up that LNK2019 error.
Also my apologies if I'm using the wrong forum. Should I move my question to the forum you linked?
#3
Stack Overflow - http://stackoverflow.com/questions/31053670/unresolved-external-symbol-vsnprintf-in-dxerr-lib
10/22/2015 (5:45 am)
No, he's set up correctly - the problem is that the Windows SDK has changed. That function (which is a Windows internal for translating strings from one of their obscure formats to another) has been deprecated. You're going to have to find out where it's called from and update it to whatever it has become. Had this issue with the DirectX error translation method that vanished too.Stack Overflow - http://stackoverflow.com/questions/31053670/unresolved-external-symbol-vsnprintf-in-dxerr-lib
#4
Although I'm pretty n00b when it comes to the dx sdk, I'll give it a shot tonight after work.
I haven't looked into the engine's architecture yet but, since we brought this up... Would it be too hard for a 2 men team to get rid of the directX monster in favor of opengl?
10/22/2015 (6:10 am)
Hey thanks for the info Richard!Although I'm pretty n00b when it comes to the dx sdk, I'll give it a shot tonight after work.
I haven't looked into the engine's architecture yet but, since we brought this up... Would it be too hard for a 2 men team to get rid of the directX monster in favor of opengl?
#5
Then you can get into working with the Torque 3D instantly and then later focus on stuff like hooking the engine up against VS 2015 ;O)
10/22/2015 (8:33 am)
What is wrong with... VS 2013 community? Just a question?Quote:Unfortunately, dxerr.lib (along with d3dx11.lib) have been deprecated. You have two options - you can switch back to VS2013 or you can stop using functionality from dxerr.lib. The latter is probably better, because you can duplicate its functionality by using FormatMessage now (more info in the linked article).
Then you can get into working with the Torque 3D instantly and then later focus on stuff like hooking the engine up against VS 2015 ;O)
#7
I also like the sizegenetics reviews that have been posted.
04/10/2016 (1:40 am)
How is VS 2013 working out for you with you John?I also like the sizegenetics reviews that have been posted.
Associate Steve Acaster
[YorkshireRifles.com]
Not using VS2015 but make sure you've set it all up correctly. torque3d.org/start/#download
And maybe try here forums.torque3d.org/