Can not compile project code
by Michael Canty · in Torque 3D Professional · 07/03/2009 (8:30 pm) · 2 replies
I am not sure this is the place to post this but I'll try. Let me know if it should go somewhere else. I am trying to make some changes to the T3D engine but when I compile the code for debug I get the below errors. Can someone tell me if I have a bad install. I have re-installed but still this problem.
Build Log Build started: Project: Steorra, Configuration: Debug|Win32
Command Lines Creating temporary file "c:\Torque\Torque 3D 2009 Beta 3\My Projects\Steorra\buildFiles\Link\VC2k8.Debug.Win32\Steorra\RSP00002437602280.rsp" with contents
[
/OUT:"../../../game/Steorra_DEBUG.exe" /INCREMENTAL /LIBPATH:"../../Link/VC2k8.Debug.Win32" /MANIFEST /MANIFESTFILE:"../../Link/VC2k8.Debug.Win32/Steorra\Steorra_DEBUG.exe.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /NODEFAULTLIB:"LIBC" /NODEFAULTLIB:"LIBCD" /DEBUG /PDB:"../../Link/VC2k8.Debug.Win32/Steorra_DEBUG.pdb" /SUBSYSTEM:WINDOWS /DYNAMICBASE:NO /MACHINE:X86 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib "..\..\..\game\steorra_debug.lib"
"..\..\Link\VC2k8.Debug.Win32\Steorra\Torque.res"
"..\..\Link\VC2k8.Debug.Win32\Steorra\main.obj"
"..\..\Link\VC2k8.Debug.Win32\Steorra\Steorra_DEBUG.exe.embed.manifest.res"
]
Creating command line "link.exe @"c:\Torque\Torque 3D 2009 Beta 3\My Projects\Steorra\buildFiles\Link\VC2k8.Debug.Win32\Steorra\RSP00002437602280.rsp" /NOLOGO /ERRORREPORT:PROMPT"
Output Window Linking...
LINK : fatal error LNK1104: cannot open file '..\..\..\game\steorra_debug.lib'
Results Build log was saved at "file://c:\Torque\Torque 3D 2009 Beta 3\My Projects\Steorra\buildFiles\Link\VC2k8.Debug.Win32\Steorra\BuildLog.htm"
Steorra - 1 error(s), 0 warning(s)
thank in advance for anyones help.
Mike
Build Log Build started: Project: Steorra, Configuration: Debug|Win32
Command Lines Creating temporary file "c:\Torque\Torque 3D 2009 Beta 3\My Projects\Steorra\buildFiles\Link\VC2k8.Debug.Win32\Steorra\RSP00002437602280.rsp" with contents
[
/OUT:"../../../game/Steorra_DEBUG.exe" /INCREMENTAL /LIBPATH:"../../Link/VC2k8.Debug.Win32" /MANIFEST /MANIFESTFILE:"../../Link/VC2k8.Debug.Win32/Steorra\Steorra_DEBUG.exe.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /NODEFAULTLIB:"LIBC" /NODEFAULTLIB:"LIBCD" /DEBUG /PDB:"../../Link/VC2k8.Debug.Win32/Steorra_DEBUG.pdb" /SUBSYSTEM:WINDOWS /DYNAMICBASE:NO /MACHINE:X86 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib "..\..\..\game\steorra_debug.lib"
"..\..\Link\VC2k8.Debug.Win32\Steorra\Torque.res"
"..\..\Link\VC2k8.Debug.Win32\Steorra\main.obj"
"..\..\Link\VC2k8.Debug.Win32\Steorra\Steorra_DEBUG.exe.embed.manifest.res"
]
Creating command line "link.exe @"c:\Torque\Torque 3D 2009 Beta 3\My Projects\Steorra\buildFiles\Link\VC2k8.Debug.Win32\Steorra\RSP00002437602280.rsp" /NOLOGO /ERRORREPORT:PROMPT"
Output Window Linking...
LINK : fatal error LNK1104: cannot open file '..\..\..\game\steorra_debug.lib'
Results Build log was saved at "file://c:\Torque\Torque 3D 2009 Beta 3\My Projects\Steorra\buildFiles\Link\VC2k8.Debug.Win32\Steorra\BuildLog.htm"
Steorra - 1 error(s), 0 warning(s)
thank in advance for anyones help.
Mike
#2
www.garagegames.com/community/forums/viewthread/96227/1#comment-646697
07/05/2009 (11:17 am)
Check through this thread and see if it helpswww.garagegames.com/community/forums/viewthread/96227/1#comment-646697
Torque 3D Owner Judy L Tyrer
It looks to me like you aren't compiling steorra_debug.lib but just trying to link with it. Several things could cause this but my first bet is that there is a build error in building steorra_debug.lib and you didn't notice it and only saw (and copied) the link errors. Scroll up in the output window or, if using VS, open the "errors" window.
One solution that can work when you can't figure out why things don't link is to just do a build clean followed by a build. This takes longer, but if the dependency files aren't up to date (are they ever?) then this will catch a case of a missed dependency. Or if you're using precompiled headers and changed a header, be sure and recompile your precompiled headers because they won't recompile on their own (*mutters something rude*)
Hope this helps.