Prev: A problem of UDP
Next: How to handle tab notifications in CTabCtrl subclass?
From: ender.a.wiggins on 30 May 2008 03:00
Hi,

I'm not very good w/ VC++ as I come from the other side, but I have a
VC++ program that did compile (inherited it), and I did a build->clean
solution on a project and I can no longer get it to link now. All the
cpp files build fine, but it doesn't link w/ another dll that's in the
Release directory of my visual studio project. I get lots of
'unresolved external symbol errors.

Can anyone help me w/ what I need to do to get it to link and create
my exec?

Thnx,
From: Giovanni Dicanio on 30 May 2008 04:08

<ender.a.wiggins(a)gmail.com> ha scritto nel messaggio
news:d7c624a5-99c2-4e0d-a454-4a4655e3ad1f(a)k13g2000hse.googlegroups.com...

> I have a
> VC++ program that did compile (inherited it), and I did a build->clean
> solution on a project and I can no longer get it to link now. All the
> cpp files build fine, but it doesn't link w/ another dll that's in the
> Release directory of my visual studio project. I get lots of
> 'unresolved external symbol errors.
>
> Can anyone help me w/ what I need to do to get it to link and create
> my exec?

Maybe you are missing some .lib file.
If you want to link with a DLL, you may use two options: #1 use a .lib file,
or #2 use LoadLibrary/GetProcAddress in your code.

If you get unresolved external symbol errors, I think that you are in case
#1, but you are missing the .lib file.

You should check to see if you have some <your DLL name>.lib file in your
solution...

Giovanni


From: ender.a.wiggins on 30 May 2008 04:23

> You should check to see if you have some <your DLL name>.lib file in your
> solution...

I found <dll name>.lib files in another directory which contains the
dll, headers, and other files to the dll I need to link with.

So I copied the *.lib files into my Release directory and then I
clicked "build solution" and I'm still seeing the same results.
From: Giovanni Dicanio on 30 May 2008 05:06

<ender.a.wiggins(a)gmail.com> ha scritto nel messaggio
news:c331d775-a681-4ef2-9eb1-b486ebdfc443(a)m36g2000hse.googlegroups.com...

> I found <dll name>.lib files in another directory which contains the
> dll, headers, and other files to the dll I need to link with.
>
> So I copied the *.lib files into my Release directory and then I
> clicked "build solution" and I'm still seeing the same results.

You may try to copy the .lib file in your project directory (or modify the
library path from the IDE, to add also the path that contains the .lib
file), and add the following line in one of your source code, after
#incldues:

#pragma comment( lib, "<< your lib name >>" )

Giovanni



From: David Ching on 30 May 2008 05:14

<ender.a.wiggins(a)gmail.com> wrote in message
news:c331d775-a681-4ef2-9eb1-b486ebdfc443(a)m36g2000hse.googlegroups.com...
>
>> You should check to see if you have some <your DLL name>.lib file in your
>> solution...
>
> I found <dll name>.lib files in another directory which contains the
> dll, headers, and other files to the dll I need to link with.
>
> So I copied the *.lib files into my Release directory and then I
> clicked "build solution" and I'm still seeing the same results.

You need to specify this library in your Project Settings. Right click the
project in the Solution Explorer window and select Properties. In the tree
on the left, click Linker, and expand it. I think there is an Input item
below it, and in that pane, there is a place to specify external
dependencies like .lib files.

-- David


 |  Next  |  Last
Pages: 1 2
Prev: A problem of UDP
Next: How to handle tab notifications in CTabCtrl subclass?