Sign in to follow this  

Link Errors with LIBCD.lib

This topic is 4763 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

On compile, I get the following list of link errors: Using NiApplication fatal error LNK1169: one or more multiply defined symbols found Using NiApplication error LNK2005: "private: __thiscall type_info::type_info(class type_info const &)" (??0type_info@@AAE@ABV0@@Z) already defined in LIBCD.lib(typinfo.obj) Using NiApplication error LNK2005: "private: class type_info & __thiscall type_info::operator=(class type_info const &)" (??4type_info@@AAEAAV0@ABV0@@Z) already defined in LIBCD.lib(typinfo.obj) Using NiApplication error LNK2005: __vsnprintf already defined in LIBCD.lib(vsnprint.obj) Using NiApplication error LNK2005: _atoi already defined in LIBCD.lib(atox.obj) Using NiApplication error LNK2005: _exit already defined in LIBCD.lib(crt0dat.obj) Using NiApplication error LNK2005: _fclose already defined in LIBCD.lib(fclose.obj) Using NiApplication error LNK2005: _fflush already defined in LIBCD.lib(fflush.obj) Using NiApplication error LNK2005: _fread already defined in LIBCD.lib(fread.obj) Using NiApplication error LNK2005: _fseek already defined in LIBCD.lib(fseek.obj) Using NiApplication error LNK2005: _ftell already defined in LIBCD.lib(ftell.obj) Using NiApplication error LNK2005: _sprintf already defined in LIBCD.lib(sprintf.obj) Using NiApplication error LNK2005: _strchr already defined in LIBCD.lib(strchr.obj) Using NiApplication error LNK2005: _strncpy already defined in LIBCD.lib(strncpy.obj) Using NiApplication error LNK2005: _tolower already defined in LIBCD.lib(tolower.obj) Anyone know how to get rid of these? Or what's causing them? I'm not redefining them, or telling it to include libcd. Thanks. -Nick

Share this post


Link to post
Share on other sites
Check to make sure that your code generation options (under project properties) for the runtime library you are using matches the runtime library settings for any libraries you are using. In most cases this means you need to set your application to build against the multithreaded DLL version of the C runtime library.

Share this post


Link to post
Share on other sites

This topic is 4763 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this