Migration

  • Thread starter Thread starter Ken
  • Start date Start date
K

Ken

Hi all,

I got a *.lib files and some header files from a thrid party which is
developed using ANSI C. I am now trying to create a managed C++ application
and import those libraries. I added the lib file in the linker option and
include those header files inside the program. Everything is ok when i
complied the project.

However, when I call one of the function inside the lib file I imported
and compile the project, a lot of multiple defined symbol error is found.
(e.g. ___argc already defined in libcmtd.lib(crt0dat.obj)). I don't know
what's wrong with it as I am new to both C++ and VC++.NET. Can anyone help
??

Kenneth
 
Ken said:
I got a *.lib files and some header files from a thrid party which is
developed using ANSI C. I am now trying to create a managed C++ application
and import those libraries. I added the lib file in the linker option and
include those header files inside the program. Everything is ok when i
complied the project.

However, when I call one of the function inside the lib file I imported
and compile the project, a lot of multiple defined symbol error is found.
(e.g. ___argc already defined in libcmtd.lib(crt0dat.obj)). I don't know
what's wrong with it as I am new to both C++ and VC++.NET. Can anyone help
Click to expand...

Maybe you included the header files more then once?
"#pragma once" might help you.

B.
 
Ken said:
Hi all,

I got a *.lib files and some header files from a thrid party which
is developed using ANSI C. I am now trying to create a managed C++
application and import those libraries. I added the lib file in the
linker option and include those header files inside the program.
Everything is ok when i complied the project.

However, when I call one of the function inside the lib file I
imported and compile the project, a lot of multiple defined symbol
error is found. (e.g. ___argc already defined in
libcmtd.lib(crt0dat.obj)). I don't know what's wrong with it as I am
new to both C++ and VC++.NET. Can anyone help ??
Click to expand...

The problem is that the library and the code you're trying to link it in to
were compiled with different runtime library settings (e.g. the library was
compiled with /MT and you're compiling with /MD). Your choices are two:

1. Re-compile the library with /MD to match your managed code.

2. Add the linker option /NODEFAULTLIB:LIBCMTD.LIB to your linker settings
(you'll likely have to add /NODEFAULTLIB:LIBCMT.LIB to the release build
configuration as well).

-cd
 
Back
Top