LINK : fatal error LNK1104: cannot open file 'C:\Program.obj
by Shawn Bullock · in Torque Game Engine Advanced · 07/10/2005 (2:16 pm) · 6 replies
Greetings,
I am using DirectX 9.0 SDK (April 2005) with VS.NET 2003.
I followed the instructions as best I can. I get this error after building:
LINK : fatal error LNK1104: cannot open file 'C:\Program.obj'
Not sure what to do with it. Any ideas? I'm sure its a simple oversight on my behalf.
Thanks,
Shawn
I am using DirectX 9.0 SDK (April 2005) with VS.NET 2003.
I followed the instructions as best I can. I get this error after building:
LINK : fatal error LNK1104: cannot open file 'C:\Program.obj'
Not sure what to do with it. Any ideas? I'm sure its a simple oversight on my behalf.
Thanks,
Shawn
About the author
#2
07/11/2005 (2:52 pm)
It's trying to link a compiled file in your root, which is odd. Where is TSE installed, and are you sure you're not compiling a program.cc or something liket that somewhere?
#3
07/11/2005 (3:09 pm)
You installed TSE into a directory path with spaces. This tends to break the compilter. Moving the code to a directory path with no spaces should fix the problem.
#4
I got it from CVS and then I made the necessary changes to reference d3d9.h/.lib and build it. After a few minutes, I got that link error.
I don't have spaces in my directory path. At least none that are obvious. I'm not a C++ programmer so I'm not terribly familiar with the vast compiler settings/options and projects options.
Thanks,
Shawn
07/11/2005 (3:37 pm)
It is installed in C:\tse\sdk\I got it from CVS and then I made the necessary changes to reference d3d9.h/.lib and build it. After a few minutes, I got that link error.
I don't have spaces in my directory path. At least none that are obvious. I'm not a C++ programmer so I'm not terribly familiar with the vast compiler settings/options and projects options.
Thanks,
Shawn
#5
The documentation seems to imply that the sdk directories can't have spaces. But when I follow the instructions to setting up the environment, they state to to add a path to the dx sdk headers/libs wherever they are installed.
Of course, you make no small fuss about making sure there are no spaces in the paths, in the same place where it says to add a path to the dx sdk headers/libs, it doesn't make it clear that there shouldn't be spaces in those paths (or at least I didn't notice where it said that) so after much contemplating, I thought it was okay since that was the only place where there wasn't a warning.
So I changed the location of the sdk headers/libs and it built successfully.
I think you should update your documentation to make it "clearer", rather than saying to choose the installation directory of the DirectX SDK, make it clear that there can't even be spaces in that directory.
Thanks,
Shawn
07/12/2005 (11:43 am)
I fixed it.The documentation seems to imply that the sdk directories can't have spaces. But when I follow the instructions to setting up the environment, they state to to add a path to the dx sdk headers/libs wherever they are installed.
Of course, you make no small fuss about making sure there are no spaces in the paths, in the same place where it says to add a path to the dx sdk headers/libs, it doesn't make it clear that there shouldn't be spaces in those paths (or at least I didn't notice where it said that) so after much contemplating, I thought it was okay since that was the only place where there wasn't a warning.
So I changed the location of the sdk headers/libs and it built successfully.
I think you should update your documentation to make it "clearer", rather than saying to choose the installation directory of the DirectX SDK, make it clear that there can't even be spaces in that directory.
Thanks,
Shawn
#6
07/12/2005 (5:44 pm)
That's good feedback Shawn, we'll try and get that in when the docs are ported to TDN. Ahh TDN.
Torque Owner Shawn Bullock
Thanks,
Shawn