Re: [xml] Link warnings .... that may be causing my COM component to not load

[Michael Ludwig <milu71 gmx de>]

Bjoern Hoehrmann schrieb am 25.11.2011 um 11:42 (+0100):
> * john murphy uk bnpparibas com wrote:
> > 1>LINK : warning LNK4098: defaultlib 'mfc80ud.lib' conflicts with
> > use of other libs; use /NODEFAULTLIB:library
> > 1>LINK : warning LNK4098: defaultlib 'mfcs80ud.lib' conflicts with
> > use of other libs; use /NODEFAULTLIB:library
>
> You are linking to MFC both dynamically and statically. You would
> have to figure out why that is and then pick one or the other
> linking method.

Not being a C pro, I was wondering how you know statically vs
dynamically is the issue here? John wrote:

| The build settings for my app are MD(d) so we are linking dynamically
| with MSVCRT.dll.  It is unfortunately using bits from the MFC also.

And there was the _AFXDLL preprocessor directive, which you'd use for
dynamic linking.

Okay, here's what I think: The two error messages at the top are for
the import library for the DLL (mfc80ud.lib - at least I think that's
an import library for the DLL) and *also* for a static library
(mfcs80ud.lib).

But on Michael Kaplan's blog I read:

  There is also a static component to even a DLL build of MFC, named
  as follows:

   MFCS80U.LIB (Unicode Release â static library â deprecated classes)
   MFCS80UD.LIB (Unicode Debug â static library â deprecated classes)

http://blogs.msdn.com/b/michkap/archive/2005/10/07/478235.aspx

So where's the undue static linking and how do you know?

-- 
Michael Ludwig