Getting #include {iostream} to work

[JaeBeam]

I am having issues writing a C++ .dll. When using MSVC++ 2003 the following line; #include <iostream> gives me a few errors OraclePingC++ 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) and OraclePingC++ 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) When I comment out the #include line, the errors go away. I've tried to play with the linker settings with my properties, but I'm not making progres..

[David Crow]

JaeBeam wrote:

When I comment out the #include line, the errors go away.

So then what's the problem?

"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

[Rajesh R Subramanian]

DavidCrow wrote:

So then what's the problem?

It is "not working". :-D

It is a crappy thing, but it's life -^ Carlo Pallini

[josda1000]

This is just supposition, but did you do this in debug mode? I see that it's trying to call malloc and free with debug mode... try in release. see what happens. but i've definitely never seen this happen before

[Lost User]

In your compiler settings look for the C/C++ Code generation section and change the Runtime library to Multi-Threaded-Debug /MTd Best Wishes, -David Delaune

[JaeBeam]

It appears I already have my my Runtime library to Multi-Threaded-Debug (/MTd) Here is the complete command line, cut and pasted from my projects properties: /Od /AI "D:\Source Code\Cardacc v5.0.xx Customs\OracleTest\OraclePingC++\Debug" /D "WIN32" /D "_DEBUG" /D "_WINDLL" /D "_MBCS" /FD /EHsc /MTd /GS /Yu"stdafx.h" /Fp"Debug/OraclePingC++.pch" /Fo"Debug/" /Fd"Debug/vc70.pdb" /W3 /nologo /c /Zi /clr /TP /FU "c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorlib.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.dll" /FU "c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\System.Data.dll" When I try to build the dll in Release mode, I receive a ton of LNK2001 and 2019 errors.

[Lost User]

JaeBeam wrote:

c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorlib.dll

Is your project suppose to be using Managed C++ because you have the /clr flag set. Best Wishes, -David Delaune

[PJ Arends]

Sometime the order that you #include header files will cause stuff like this to happen because one header expects another to be included first. Try changing the order of your #includes.

---

You may be right I may be crazy -- Billy Joel -- Within you lies the power for good - Use it!

[CPallini]

Rajesh R Subramanian wrote:

It is "not working".

It's not working, plz send me codez, urgentz plz plz. FFY :-D

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]

[Rajesh R Subramanian]

Now I understand. The low vote is because I missed the important information. :laugh:

It is a crappy thing, but it's life -^ Carlo Pallini