Sorry your browser is not supported!

Hi,
I am trying to include a very basic class with my dark GDK program. The header looks like this,

My program works fine without this class but as soon as I include it I get the following 5 unresolved external symbol errors. What is going on?

-----------------------errors-----------------------

Error 2 error LNK2019: unresolved external symbol __CrtDbgReportW referenced in function "public: char const & __thiscall std::_String_const_iterator<char,struct std::char_traits<char>,class std::allocator<char> >::operator*(void)const " (??D?$_String_const_iterator@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QBEABDXZ) libcpmtd.lib


Error 3 error LNK2001: unresolved external symbol __CrtDbgReportW libcpmtd.lib

Error 4 error LNK2019: unresolved external symbol __malloc_dbg referenced in function "void * __cdecl operator new(unsigned int,struct std::_DebugHeapTag_t const &,char *,int)" (??2@YAPAXIABU_DebugHeapTag_t@std@@PADH@Z) libcpmtd.lib

Error 5 error LNK2019: unresolved external symbol __free_dbg referenced in function "void __cdecl operator delete(void *,struct std::_DebugHeapTag_t const &,char *,int)" (??3@YAXPAXABU_DebugHeapTag_t@std@@PADH@Z) libcpmtd.lib

Error 6 error LNK2019: unresolved external symbol __calloc_dbg referenced in function __Getctype libcpmtd.lib

That usually comes only in debug mode. If you can compile it in release mode then the problem is that you need to go into the project settings of the debug compile and set the c/c++ code generation runtime library to /MT instead of /MTd.

It could be because you are calling #include<iostream>, i am not 100% on this but if you have alreddy called <iostream> in main you may be calling it again when you include your object.

I sugest tacking out all funcinality, than adding back the functions one at a time untill you see what is causing the problem



also try tacking out the #pragma once


then put these 2 lines at the top

#ifndef NOTE
#define NOTE


and this one at the very bottom

#endif

Im not real great at c++ my self but dont you need an override:

Note(void);
Note(int vPos, int hPos, char type);
~Note(void);

just a guess...and it is how I Got it to compile on my PC

That shouldn't be the issue. Including a header twice, especially a system header, shouldn't cause such a conflict. It should include at least a #pragma to only be included once or other preprocessor directives to prevent the same. Calling an include twice without such protection would likely cause the compiler to complain or warn about redefines but shouldn't cause a library conflict.

I'm not sure what the problem is but never use using namespace in a header as it'll enable it for all files that include this header.