asked on

VC++ 6.0 builds release, but not debug

Using VC++ 6.0, my release version builds without any trouble, but the debug version gives me 3 LNK2001 errors. After having read sveral articles in the help online, I'm no closer to understanding why. The help states that the reverse seems te be more frequent..that is, having a working debug version and the release version won't build. Can anyone shed some light on this for me? Thanks!

nietod

It would be helpful to know what the errors are--what symbols does it complain about?

ASKER CERTIFIED SOLUTION

amitc011599

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

pigeonbr

ASKER

Hi! When building, the compiler complains as follows:

--------------------Configuration: Pieces3CLR - Win32 Debug--------------------
Linking...
Pieces3CLRView.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall CPieces3CLRView::Dump(class CDumpContext &)const " (?Dump@CPieces3CLRView@@UBEXAAVCDumpContext@@@Z)
Pieces3CLRView.obj : error LNK2001: unresolved external symbol "public: virtual void __thiscall CPieces3CLRView::AssertValid(void)const " (?AssertValid@CPieces3CLRView@@UBEXXZ)
Pieces3CLRView.obj : error LNK2001: unresolved external symbol "public: class CPieces3CLRDoc * __thiscall CPieces3CLRView::GetDocument(void)" (?GetDocument@CPieces3CLRView@@QAEPAVCPieces3CLRDoc@@XZ)
\Debug/Pieces3CLR.exe : fatal error LNK1120: 3 unresolved externals
Error executing link.exe.

Pieces3CLR.exe - 4 error(s), 0 warning(s)

In the release version, no trouble. I await your interpretation. Thanks for responding!
Bruce
(pigeonbr)

nietod

Are these functions defined in CPieces2CLRVuew.cpp? Are then in closed conditional code (#if), so they might not be included in a release version?

amitc011599

What is going wrong is that your prgram is not finding the debug MFC libraries. This is typically MFCxxD.lib or MFCxxUD.lib, where xx is the MFC version, 60 in your case.

You will need to copy these files or do a reinstall of VC 6.0 and select all the MFC library options.

pigeonbr

ASKER

amitc:
I verified that MSVCRTD.LIB, LIBCD.LIB and LIBCMTD.LIB were all installed and that in the Tools->Options->Directories menu that all files and paths were ok. All seeme to point to the right directories.I tried to re-install VC 6.0 the same way I had, that is , by selecting all the options, so as not to miss anything, but with the same result. The program I was working on was started in VC 4.0 and when I got VC 6.0, I imported it, seemingly with success, but the debug doesnt want to work, and I had no problems with eithere release or debug in VC 4.0. I still have 4.0 on my pc, but I don't believe this is affecting anything. If you have any more ideas, let me know. I will attempt to get some help from Microsoft this week comeing thru their telephone support, but don't bargain on much FREE help from them..hahaha....thanks...I await your return
pigeonbr
Quebec Canada