Linking problems with 4.2b Patch
Norman L. Scroggins -- NSCROGGI@us.oracle.com
Sunday, October 06, 1996
Environment: VC++ 4.2b WinNT 4.0
I downloaded, installed the patch and rebuilt my entire project. However,
now my project cannot link. I get unresolves involving the all the
common control classes (.ie CListCtrl, CTreeCtrl, CTabCtrl) and their
methods. Has anyone had this problem? Any ideas as to why this happens?
Norman
Mike Blaszczak -- mikeblas@nwlink.com
Monday, October 07, 1996
[Mini-digest: 3 responses]
At 19:48 10/6/96 PDT, "Norman L. Scroggins" wrote:
>Environment: VC++ 4.2b WinNT 4.0
>I downloaded, installed the patch and rebuilt my entire project. However,
>now my project cannot link. I get unresolves involving the all the
>common control classes (.ie CListCtrl, CTreeCtrl, CTabCtrl) and their
>methods. Has anyone had this problem? Any ideas as to why this happens?
It would be dreamy if you could provide the specific error messgaes.
But as a blind guess, I'd say that you are getting a bad version of
COMMCTRL.H someplace along the way. That might be because:
1) You didn't patch the header files
2) You have old and new header files and are including the
wrong ones when you build
3) You did patch the files and something went wrong and COMMCTRL.H
itself wasn't patched.
Maybe the problem came about another way. Since you didn't bother to
share the exact error message, I'm forced to just guess. But maybe another
problem is that you've patched the headers but not the libraries:
1) You didn't patch the libraries, period
2) You have old and new library files and are linking to the wrong
ones when you build
3) You did patch the libraries and something went wrong and the particular
MFC library you end up linking with itself wasn't patched.
The names of some symbols changed between MFC 4.2 and MFC 4.2b. This was
unavoidable because the declarations in the system header files changed.
There's nothing that could be done but fix the problem in the way that
we did. If you're having problems linking to the common controls, it's
probably because the linker (or the compiler) wants the old names and the
compiler (or the linker) got the new names.
Maybe there are other ways to cause the symptom you mention--since you didn't
bother to provide the exact linking options and build mode of your project,
and you didn't show us the exact error message, these are just guesses. But
with that information, it might not be hard to exactly nail the configuration
problem you have.
.B ekiM
http://www.nwlink.com/~mikeblas/
Don't look at my hands: look at my _shoulders_!
These words are my own. I do not speak on behalf of Microsoft.
-----From: David Little
Make sure you are using the right includes. You might be copying one from another directory on your include path.....
-----From: mss@tartus.com (Michael Scherotter)
I got similar problems with CListCtrl. I had to rebuild all.
Then it worked.
--
Michael S. Scherotter |Architectural Design Tools
Lead Software Developer |AutoCAD Applications
Tartus Development, Inc. |Custom CAD Solutions
630 Las Gallinas Ave #300 |__________________________
San Rafael, CA 94903 mss@tartus.com
(415) 491-8925 michael@charette.com
(415) 491-8921 (fax) 71035.1675@compuserve.com
http://www.tartus.com/people/mss
____________________________________________________________
| Вернуться в корень Архива
|