C4c --- Link Error: Unresolved External 
Author Message
 C4c --- Link Error: Unresolved External

Quote:

> Hi, and yes I'm new to DLL's

To get dlls to work remember the golden rule.  The dll has to export
its functions and in the exe the same procedure needs to be declared
external. Think of declaring a proc as external as inviting import of
that procedure.  In your case, the exe doesnt seem to know that the
procedure in the dll is external.  To tell it, add an external dll
template procedure with the name and prototype of the procedure in the
dll you are calling. That will add the external attribute, and the
dll() attribute plus tell CW to link the .lib file for the dll.

To trouble shoot, in the exe look at the generated source, make sure
the procedure from the dll is prototype in a map with the external
attribute and dll attribute.  Then look at the .exp file for the dll
and make sure the procedure in question is being exported.  When both
halves of the equation are taken care of you'll be much happier.
---
Jim Kane  - TeamTopSpeed
Productive Software Solutions
Can't Find that Message?
Get Organized, Get ForKeeps!
www.fkeeps.com



Sun, 08 Jul 2001 03:00:00 GMT  
 C4c --- Link Error: Unresolved External
Jimj,

ARNOR AND STEVE TIP ALERT
-----------------------------------------------------

Quote:
>To get dlls to work remember the golden rule.  The dll has to export
>its functions and in the exe the same procedure needs to be declared
>external. Think of declaring a proc as external as inviting import of
>that procedure.  In your case, the exe doesnt seem to know that the
>procedure in the dll is external.  To tell it, add an external dll
>template procedure with the name and prototype of the procedure in the
>dll you are calling. That will add the external attribute, and the
>dll() attribute plus tell CW to link the .lib file for the dll.

>To trouble shoot, in the exe look at the generated source, make sure
>the procedure from the dll is prototype in a map with the external
>attribute and dll attribute.  Then look at the .exp file for the dll
>and make sure the procedure in question is being exported.  When both
>halves of the equation are taken care of you'll be much happier.
>---
>Jim Kane  - TeamTopSpeed
>Productive Software Solutions
>Can't Find that Message?
>Get Organized, Get ForKeeps!
>www.fkeeps.com

This is an absolutely wonderful explanation. Thanks.


Mon, 09 Jul 2001 03:00:00 GMT  
 C4c --- Link Error: Unresolved External
Hi Robert,


Quote:

>ARNOR AND STEVE TIP ALERT

IKB'd<g>

Best regards,

Arnor Baldvinsson        
[Team Topspeed - Internet Connect]
Allerup Edb
Denmark

http://www.icetips.com  (http://199.34.26.68)
UIN nr.: 2428601



Mon, 09 Jul 2001 03:00:00 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. C4c --- Link Error: Unresolved External

2. Link Error: Unresolved External _CLAFindWindow@ in .....

3. Link Error: Unresolved External Wsl@LibInstance in BTRWON.OBJ

4. Link Error - Unresolved External (C4bg ABC)

5. Link Error: Unresolved external file

6. Link Error: UNRESOLVED EXTERNAL Datafixes @F - in MAIN(FRAME)

7. Link Error: unresolved external CLARION

8. Link Error: Unresolved External

9. Linking Error - Unresolved External DOS in Marke045.obj

10. Unresolved external link errors in 32-bit

11. Link Error: Unresolved external GETWINDOWTASK

12. Link Error - Unresolved external GETMODULEMESSAGE in XXX002.obj

 

 
Powered by phpBB® Forum Software