View Full Version : Unresolved references error upon linking

07-08-2010, 01:29 PM
Hi All
I am using the RogueWave library with VS2004 and all compiles perfectly. But I get a bunch of linker errors, three of which I have listed below. I must be missing some file references in the link instructions. Maybe someone with more experience can tell me what I am missing?
Thanks In Advance
Alan Young

===error 1====
windx error LNK2019: unresolved external symbol "public: virtual __thiscall

CDlgYesNoCancel::~CDlgYesNoCancel(void)" (??1CDlgYesNoCancel@@UAE@XZ) referenced

===error 2====

function "public: int __thiscall CPatientDoc::CanCancelDocument(void)" (?


===error 3====

WinDX.obj : error LNK2019: unresolved external symbol "public: __thiscall

CDlgBatchOperations::CDlgBatchOperations(class CWnd *)" (??

0CDlgBatchOperations@@QAE@PAVCWnd@@@Z) referenced in function "public: void

CWinDXApp::OnBatchOperations(void)" (?OnBatchOperations@CWinDXApp@@QAEXXZ)

==== link instructions ======

/VERBOSE /OUT:".\..\bin\debug/windx.exe" /VERSION:2.1 /INCREMENTAL /NOLOGO

/LIBPATH:"..\bin\Debug" /LIBPATH:"..\OT803\Lib" /LIBPATH:"C:\Program

Visual Studio .NET 2003\Vc7\lib" /LIBPATH:"C:\Program Files\Microsoft Visual
Studio .NET

2003\Vc7\atlmfc\lib" /LIBPATH:"..\WinDX\RogueWavelib" /LIBPATH:"C:\Program

Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\Lib"

/DEBUG /PDB:".\..\bin\debug/windx.pdb" /SUBSYSTEM:WINDOWS /MACHINE:X86

OSC60asd.lib winmm.lib version.lib SSComLib.lib DBConvertLib.lib DelayImp.lib

\windx2.net\Cbiidotnet\WinDX\bin\Debug\DBVerify.li b

\windx2.net\Cbiidotnet\WinDX\bin\debug\StdCalibrat ion.lib

\windx2.net\Cbiidotnet\WinDX\ProductId\Debug\Produ ctId.lib

\windx2.net\Cbiidotnet\WinDX\bin\Debug\DBExportSQL .lib "\Program Files\Rogue

Wave\Stingray Studio\lib\RWUXThemeSD.lib" DelayImp.lib

08-17-2010, 04:26 PM
wow nobody has responded yet

08-18-2010, 11:08 AM
CDlgYesNoCancel, CPatientDoc, and CDlgBatchOperations are not Stingray classes. I assume they are in your code somewhere.

Look through your code for these classes and see where the errant functions are declared. Then see if they are defined anywhere and be sure the module in which they are defined is included in your link.