On Mar 1, 11:52 pm, pauldepst...@att.net wrote:
Can anyone advise or provide a URL for this problem?
http://vcfaq.mvps.org/lang/10.htm
First Google result for LNK1104.
Perhaps this
isn't a language question,
It's not.
and I apologise if I'm slightly OT
You are.
but this
is a very urgent matter for me so I was keen to pick among the high-
activity newsgroups.
I guess I've been there, too. You probably aren't going to hell.
Although from now on you should stick to relevant newsgroups; these
ones are high-activity enough already. In your case, it might be
something like microsoft.public.dotnet.languages.vc or
microsoft.public.vc; but don't quote me on that.
Thank you very much for your help,
That said:
1) Make sure ProjectName.lib actually exists somewhere.
2) Make sure ProjectName.lib is in your library path. If you need a
quick fix, find ProjectName.lib, and specify the absolute path in your
additional library directories as per the instructions in the link
above. For example, if you have "c:\somewhere\ProjectName.lib", add "c:
\somewhere" to your library directories. You could also just specify
the absolute path in the library list; instead of "..\..
\ProjectName.lib", change it to "c:\whatever\ProjectName.lib" -- or
just remove the path entirely, leave it as "ProjectName.lib", make
sure it's in your library path, and VC should find it.
You did not give enough information for a more specific answer. In
general, when you link to .lib files, the linker will search the
library paths you have defined. If you link to "..\a.lib" then it will
look for that relative path in the library paths you have set up, so
if "C:\whatever" is a library path, it will look for "c:\whatever\..
\a.lib", which is just "c:\a.lib". So be aware of that, too. If that
makes sense.
Sorry for the sloppy answer, it's all I can think about right now.
It's getting late.
Also, again, this isn't the place to ask, so I would not get your
hopes up too high.
Jason