Link problem with Profiler in VC++ 6.0
Mike,
Take a look at the following article:
http://support.microsoft.com/support/kb/articles/Q109/2/69.asp
Looks like the lib you are linking with, is a debug one, it came without its
own pdbd, and now it tries to pull in missing information from a default pdb
file, which happens to be yours. Rename it by using /Fd:"MyFoo.pdb". You will
gets lots of warnings, but the link will go through.
HTH
Eugene.
Quote:
> I forgot to add that when I create my dll file with Enable Profiling
> *unchecked* (all other things equal), the build/link process completes
> just fine.
> >I am trying to build a dll file with options Enable Profiling and
> >Generate mapfile checked in Project|Settings|Link. However,
> >the linking fails with:
> > Linking...
> > Creating library .../Debug/mine.lib and object .../Debug/mine.exp
> > external.lib(eobj.obj) : fatal error LNK1202: "...\Debug\vc60.pdb"
> > is missing debugging information for referencing module
> > Error executing link.exe.
> > Creating browse info file...
> > mine.dll - 1 error(s), 0 warning(s)
> >Note that I changed some of the names and put ...\ because they are
> >not relevant. The problem seems to stem from the fact that my own
> >mine.dll links to external.lib for which I do not have any source code
> >just the library itself. It could be created with debug option but
> >maybe *without* the profiling option.
> >Consequently, the question is whether it is necessary for the
> >library (which is being linked to) to be created with profiling option
> >itself in order for your own dll file (which links to
> >this library) to be created with profiling option. If this is really
> >the cause what are the steps to get around the problem because I will
> >not be able to get a new version of the library any time soon.
Sent via Deja.com http://www.deja.com/
Before you buy.
