ansaurus

Question

Linker Errors C++ Visual Studio 2005

Answer 1

+1 A:

The link error seem to be complaining about the lack of a lot of MFC functions, and you link lines includes: /NODEFAULTLIB:"nafxcwd.lib" which would exclude MFC. Is the lib you are linking against built with MFC?

Other things to check are that you are compiling the app and the lib with the same character set (ie. both multibyte or both unicode).

When you are building a lib there is no link step, so an arbitrary collection of objects can be thrown into a lib without any regard for what else they might need.

Rob Walker 2008-10-27 18:16:40

Actually, I set libcmtd.lib and nafxcwd.lib to ignore, as I was receiving a number of LNK2005 errors for those. See: error LNK2005: "public: virtual void __thiscall CWnd::PreSubclassWindow(void)" (?PreSubclassWindow@CWnd@@UAEXXZ) already defined in mfc80ud.lib(MFC80UD.DLL)

Gopherkhan 2008-10-27 18:39:05

It is always helpful to understand what is the source of the link request for nafxcwd then. Why does the app think it needs to link it in -- as Scott says it sounds like the components are built will different CRT or MFC settings.

Rob Walker 2008-10-27 18:54:57

Answer 2

A:

It looks like your project is linking with the Debug Multithreaded runtime. Is this your intention? If so there may be inconsistencies with the KeyCapture_Config library that you seem to be using.

Is KeyCapture_Config a 3rd party library? If so did you build it from source or was the lib/dll provided for you?

It may just take some investigation on which C/C++ runtimes are being built against. You can reference the Microsoft KB Article that might help shed some light on the possible runtime build discrepancies.

Scott Saad 2008-10-27 18:27:10

The actual Project I'm integrating with can be found here:http://dynamicnetservices.com/~will/academic/textinput/keycapture/Runtime Library is set to Multi-threaded Debug DLL (/MDd). Should I be doing this somewhere else?

Gopherkhan 2008-10-27 18:41:12

thanks for the article link

Gopherkhan 2008-10-27 18:46:41

Answer 3

A:

I think that Rob Walker has nailed the problem. If the documentation for KeyCapture_Config.lib says no linkage to MFC, check the source for directives that require linkage to MFC. Something like this:

#pragma comment(lib, "nafxcwd.lib")

would cause a dependency on MFC, and the KeyCapture_Config.lib doc may be out of date.

rschuler 2008-10-27 18:55:36

Answer 4

+5 A:

The library KeyCapture_Config.lib is using MFC GUI classes (CWnd, CWinApp, etc), but the application you're linking it into is a console application (see the /SUBSYSTEM:CONSOLE option in your linker command line). This won't work. You should create a new MFC GUI application project and add the library to that project.

Edit: I've just checked the link in your comment: http://dynamicnetservices.com/~will/academic/textinput/keycapture/ and it seems that KeyCapture_Config is actually an MFC dialog application that uses the KeyCapture DLL. It may be possible to use KeyCapture in a console application by linking directly against KeyCapture.lib.

ChrisN 2008-10-27 19:31:37

ansaurus

tags:

views:

answers:

Linker Errors C++ Visual Studio 2005

related questions