Game Development Community

1>LINK : fatal error LNK1104: cannot open file '....linkvc2k5.debug.win32torque3dTorque.res'

by Peter Mowry · in Torque 3D Professional · 05/19/2009 (11:02 pm) · 2 replies

1>LINK : fatal error LNK1104: cannot open file '....linkvc2k5.debug.win32torque3dTorque.res'

This is what happens when I build the solution, visual studio 2005 vista x64... Version 8.0.50727.867 (vsvista.050727-8600)

I tried clean solution, then rebuild solution... In Debug mode. Release build built fine, but Debug mode has that error.

Anyone else run into this?


#1
05/20/2009 (5:43 am)
I have seen something similar, but not exactly the same. Check to see if that file has the read only file set. If not, reboot your machine and then try to rebuild to see it that fixes the issue.

What I've seen is that certain of the generated files (in your case the .res file, in my case I've seen it with Torque3D.dll and my game .exe) have been locked/are currently being accessed by some other program. You can tell if you go an physically try to delete the file and you get a message from the OS telling you that's the case.

If that solves your problem then its likely there is some kind of bug with the toolbox and it failing to relinquish its hold on the files it uses/spawns. The particular file your are having issues with cast doubt on this, however.
#2
05/20/2009 (10:50 am)
Yes, reboot and rebuild fixed the build. Yes good point, I also experienced something similar with Torque3D.dll and Torque3D_Debug.dll

However, the strange thing is that I was getting this error even though Torque.res did not exist for me. I wonder if this means Windows lets an application have a lock on a file that does not exist? Strange...

Anyway, yes rebooting . But, like you said, maybe it's actually a bug in (the Torqe Toolbox or the torque game application etc) not releasing its lock on the file.

...

I now get a new message box error when I actually run it:

[]enginesourcegfxglgfxgldevice.win.c...
GL_RENDERER returned NULL!

And the terrain is missing, and there's more messages on the console... But I can look at that next. Anyway, now it at least builds :-), thanks