Hi,
When i build my project i have the following linking errors:
nafxcwd.lib(afxmem.obj) : error LNK2005: "void * __cdecl operator
new(unsigned int)" (??2@YAPAXI@Z) déjà défini(e) dans
libcpmtd.lib(newop.obj)
nafxcwd.lib(afxmem.obj) : error LNK2005: "void __cdecl operator
delete(void *)" (??3@YAXPAX@Z) déjà défini(e) dans
libcmtd.lib(dbgdel.obj)
For information, i'm working on the C++.NET language and i'm using a
software solution api with external libraries. I encountred a similar
problem when working on a win32 console application project and i
resolved it by ignoring the libraries that caused the problem and
reinserting them in the right order (in the project properties). When i
took the same code into a C++.NET project, this procedure didn't work.
Can anyone help me solving this problem !!!
Visual C++.NET : LNK2005
Started by lin_space, Oct 05 2006 10:23 AM
2 replies to this topic
#1
Posted 05 October 2006 - 10:23 AM
#2
Posted 05 October 2006 - 10:57 AM
Oh my god, a french linker 
Well, my french is a bit rusty, but "déjà défini(e) dans" translates to "already defined in", right? It appears that you're using multiple libraries that each include their own operator new() implementation. It also appears that this problem is known by microsoft: http://support.micro...com/kb/q148652/ (first hit on google when searching for nafxcwd.lib)
Well, my french is a bit rusty, but "déjà défini(e) dans" translates to "already defined in", right? It appears that you're using multiple libraries that each include their own operator new() implementation. It also appears that this problem is known by microsoft: http://support.micro...com/kb/q148652/ (first hit on google when searching for nafxcwd.lib)
C++ addict
-
Currently working on: the 3D engine for Tomb Raider.
-
Currently working on: the 3D engine for Tomb Raider.
#3
Posted 05 October 2006 - 12:21 PM
I tried the microsoft first solution (ordering the libraries) before submitting to this group, but without any result; and i didn't understand how i can use the second solution : i set the "/verbose:lib" in the linker command line and didn't know how to procede to locate and correct the module that causes the problem !!!
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











