TSE_DEBUG.exe 3 errors
by Hokuto · in Torque Game Engine Advanced · 03/19/2005 (1:27 pm) · 18 replies
Hi there...
I just bought the EA license for TSE.
Went through the starting guide...
Latest DX
DX EXTRA for VC6 (dxsdk_feb2005_extras.exe)
Latest nVidia Drivers
DX property set up for D3D (Debug Output and Debug version settings)
ran the .reg file from the VC6 folder from TGE as I bought TGE last week
Made sure that the XD SDK include is at the top of the Tools-Options-Show Directories-include files
Same for library files... mine end in Lib\x86
which should be ok
THEN
At first I choosen to download the latest HEAD,
that didn't compile... mmm.. well it did but with 3 errors...
not sure what the errors were but they may have been the same I pasted below
So I decided to change and get the latest stable release
Release_0_2_0
But I still get 3 errors:
when it stat to Link
--------------------Configuration: Torque Shader Engine - Win32 Debug--------------------
Linking...
dxerr9.lib(dxerr9.obj) : error LNK2001: unresolved external symbol ___security_cookie
dxerr9.lib(dxerr9.obj) : error LNK2001: unresolved external symbol @__security_check_cookie@4
../example/TSE_DEBUG.exe : fatal error LNK1120: 2 unresolved externals
Error executing link.exe.
TSE_DEBUG.exe - 3 error(s), 0 warning(s)
I'm happy to have gone TSE, I can't wait to get it to compile:)
Anyone able to help?
Thanks
I just bought the EA license for TSE.
Went through the starting guide...
Latest DX
DX EXTRA for VC6 (dxsdk_feb2005_extras.exe)
Latest nVidia Drivers
DX property set up for D3D (Debug Output and Debug version settings)
ran the .reg file from the VC6 folder from TGE as I bought TGE last week
Made sure that the XD SDK include is at the top of the Tools-Options-Show Directories-include files
Same for library files... mine end in Lib\x86
which should be ok
THEN
At first I choosen to download the latest HEAD,
that didn't compile... mmm.. well it did but with 3 errors...
not sure what the errors were but they may have been the same I pasted below
So I decided to change and get the latest stable release
Release_0_2_0
But I still get 3 errors:
when it stat to Link
--------------------Configuration: Torque Shader Engine - Win32 Debug--------------------
Linking...
dxerr9.lib(dxerr9.obj) : error LNK2001: unresolved external symbol ___security_cookie
dxerr9.lib(dxerr9.obj) : error LNK2001: unresolved external symbol @__security_check_cookie@4
../example/TSE_DEBUG.exe : fatal error LNK1120: 2 unresolved externals
Error executing link.exe.
TSE_DEBUG.exe - 3 error(s), 0 warning(s)
I'm happy to have gone TSE, I can't wait to get it to compile:)
Anyone able to help?
Thanks
#2
ok
I'll give it a try... or may I actually buy Visual C++ .NET Standard 2003
I'll check on the documentation and forums to make sure .net2003 will be supported buy GG, if yes am I go that way
Thanks Stefano
Ciao
03/19/2005 (4:08 pm)
Ah,ok
I'll give it a try... or may I actually buy Visual C++ .NET Standard 2003
I'll check on the documentation and forums to make sure .net2003 will be supported buy GG, if yes am I go that way
Thanks Stefano
Ciao
#3
03/19/2005 (5:40 pm)
I do all of my TSE development in Visual Studio 7.1 (aka .net 2003). It is supported. That's why there's a vc7 directory in the TSE checkout.
#4
so 7.1 and .net 2003 is the same... I didn't know that
I guess GG will keep supporting .net 2003 for some time?... even when VC++ 2005 will be out...?
Well mind you, I guess there will be an upgrade path from 2003 to 2005 version from MS
03/20/2005 (1:30 am)
Oh right...so 7.1 and .net 2003 is the same... I didn't know that
I guess GG will keep supporting .net 2003 for some time?... even when VC++ 2005 will be out...?
Well mind you, I guess there will be an upgrade path from 2003 to 2005 version from MS
#5
In vc6 I get the same error described above, the same three errors.
When compiling with VC7 I get a whole slew of errors mostly revolving around:
error LNK2001: unresolved external symbol __RTC_CheckEsp
03/28/2005 (10:14 pm)
I had TSE compiling a few months ago, hadn't touched it in a while. Last night I got a fresh copy from the CVS and I can't get it to compile either. I've tried with both VC6 and with VC7.1, with the Summer 2004 DX update and with the Feb of 2005..In vc6 I get the same error described above, the same three errors.
When compiling with VC7 I get a whole slew of errors mostly revolving around:
error LNK2001: unresolved external symbol __RTC_CheckEsp
#6
The security cookie compile problem occurs because you don't have the Extras update for whichever DX you got
03/29/2005 (4:41 pm)
If you are using VC6, I believe the last supported DirectX release was the December one. I'm still using the October release and VC6 and it's running OK.The security cookie compile problem occurs because you don't have the Extras update for whichever DX you got
#7
I'm getting the 3 errors mentioned above with the Feb05 SDK; when I rolled back to Dec04 I got 80 errors (I did double check the directory paths) so I went back to Feb05. Oct04 wasn't on the MS site anymore, so I went back Feb05 and grabbed the extras and symbols files posted by MS and unzipped them to the SDK folder.
So, now I'm back to the original 3 errors, even after I have added the only Lib and Include folders I could find from the extras. Is there a step I'm missing with setting up the Extras update?
Thanks,
Don
Edit:
I forgot to mention I'm using Visual Studio 6
04/16/2005 (7:00 am)
@Brian Hmm - I've read through the threads on this and still haven't had any luck. Granted, I'm an artist with minimal coding experience, so that's got to be a factor. =) I had no trouble setting up WinCvs, and downloaded the latest Release instead of Head.I'm getting the 3 errors mentioned above with the Feb05 SDK; when I rolled back to Dec04 I got 80 errors (I did double check the directory paths) so I went back to Feb05. Oct04 wasn't on the MS site anymore, so I went back Feb05 and grabbed the extras and symbols files posted by MS and unzipped them to the SDK folder.
So, now I'm back to the original 3 errors, even after I have added the only Lib and Include folders I could find from the extras. Is there a step I'm missing with setting up the Extras update?
Thanks,
Don
Edit:
I forgot to mention I'm using Visual Studio 6
#8
04/16/2005 (1:46 pm)
Did you make sure that the extras lib and include directories show up BEFORE the normal lib and include directories? It might be using the normal libs rather than the VC6 compatible ones, if you have the directory order wrong.
#9
I was reading the DirectX info and also added the following environment variable:
SymPath = C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Extras\Symbols\Debug\x86\WinXP\dll;C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Extras\Symbols\Debug\x86\dll;C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Extras\Symbols\Debug\x86\exe;
Looking at that I have to ask, I know the TSE can't have spaces in the path, but would it matter to the engine that the project and environment paths do?
Thanks,
Don
04/16/2005 (2:00 pm)
Thanks for the tip, Ben. I hadn't but I just changed it and did a 'Rebuild all' with the same results.I was reading the DirectX info and also added the following environment variable:
SymPath = C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Extras\Symbols\Debug\x86\WinXP\dll;C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Extras\Symbols\Debug\x86\dll;C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Extras\Symbols\Debug\x86\exe;
Looking at that I have to ask, I know the TSE can't have spaces in the path, but would it matter to the engine that the project and environment paths do?
Thanks,
Don
#11
C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Lib\x86
and
C:\PROGRAM FILES\MICROSOFT DIRECTX 9.0 SDK (FEBRUARY 2005)\EXTRAS\DIRECTSHOW\INCLUDE
C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Include
I'm about to wipe all SDK folders and install without spaces. I'll edit this and let you know the results.
- Don
Edit:
Well, I wanted it to do something...
I'm tired so I'll look at this with fresh eyes later.
04/16/2005 (8:52 pm)
C:\PROGRAM FILES\MICROSOFT DIRECTX 9.0 SDK (FEBRUARY 2005)\EXTRAS\DIRECTSHOW\LIB\X86C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Lib\x86
and
C:\PROGRAM FILES\MICROSOFT DIRECTX 9.0 SDK (FEBRUARY 2005)\EXTRAS\DIRECTSHOW\INCLUDE
C:\Program Files\Microsoft DirectX 9.0 SDK (February 2005)\Include
I'm about to wipe all SDK folders and install without spaces. I'll edit this and let you know the results.
- Don
Edit:
Well, I wanted it to do something...
--------------------Configuration: ljpeg - Win32 Debug-------------------- Compiling... Error spawning cl.exe TSE_DEBUG.exe - 1 error(s), 0 warning(s)
I'm tired so I'll look at this with fresh eyes later.
#12
04/17/2005 (1:20 am)
Do note that you're linking against some DirectShow libs, not the Direct3d ones. This could be part of the problem...
#13
I was aware that I was linking into the Directshow folders, but that was the only place in the Extras or Symbols folders which had a lib and include folder. All the files are .pdb files, and for the life of me I haven't been able to find any information on that filetype.
My rebuild this morning was without the extras folders linked, so there was apparently no real impact by having them linked before. I'm pretty confident this is something simple, it's just my lack of familiarity with Visual Studio and C++ working against me, I fear.
Thanks for taking the time to offer help Ben, I really apprecaite it.
Regards,
Don
04/17/2005 (10:47 am)
It appears that I managed to completely mess up the directories, so I uninstalled everything except TSE this morning and re-installed cleanly. This includes Visual Studio service pack 5 and 6, and I'm back to the original errors. I was aware that I was linking into the Directshow folders, but that was the only place in the Extras or Symbols folders which had a lib and include folder. All the files are .pdb files, and for the life of me I haven't been able to find any information on that filetype.
My rebuild this morning was without the extras folders linked, so there was apparently no real impact by having them linked before. I'm pretty confident this is something simple, it's just my lack of familiarity with Visual Studio and C++ working against me, I fear.
Thanks for taking the time to offer help Ben, I really apprecaite it.
Regards,
Don
#14
04/17/2005 (3:20 pm)
Maybe it's time to upgrade to VC7... ;)
#15
04/17/2005 (4:50 pm)
Unfortunately, for some of us that would also mean upgrading to XP. :/
#16
I dug harder and found the links to the Oct SDK release and installed it and the Extras files. It compiled no problem and is running in the background as I reply. As a tangent, I really *should* go ahead and upgrade VS, but honestly until I have a better handle on programming, and determine how much time I'm going to put into it, my first purchases are always my art upgrades. ;)
Thanks *very* much to everyone for offering suggestions and instructions, I really appreciate it. =)
Regards,
Don
For those who might need the Oct SDK as well:
www.microsoft.com/downloads/details.aspx?FamilyID=b7bc31fa-2df1-44fd-95a4-c25554...
www.microsoft.com/downloads/details.aspx?FamilyID=d6f237de-a6ee-4ded-8bb6-139536...
04/17/2005 (6:58 pm)
@Ben: This bleeds over into the other thread about the missing dll, so I'm writing a generic-ish response for both.I dug harder and found the links to the Oct SDK release and installed it and the Extras files. It compiled no problem and is running in the background as I reply. As a tangent, I really *should* go ahead and upgrade VS, but honestly until I have a better handle on programming, and determine how much time I'm going to put into it, my first purchases are always my art upgrades. ;)
Thanks *very* much to everyone for offering suggestions and instructions, I really appreciate it. =)
Regards,
Don
For those who might need the Oct SDK as well:
www.microsoft.com/downloads/details.aspx?FamilyID=b7bc31fa-2df1-44fd-95a4-c25554...
www.microsoft.com/downloads/details.aspx?FamilyID=d6f237de-a6ee-4ded-8bb6-139536...
#18
04/17/2005 (10:19 pm)
I don't believe you can develop on Win98 anymore, but it will run without problems with VC6... assuming you can get it properly set up. 
Torque Owner Stefano Grippa
Give it a try, in my case it compiled like a charm.
Edit : I mean the only stable release of directx 9 (october 2004) not TSE.