Link Warning message question
I'm using VC++ 6.0 and MFC. My workspace
has 2 projects -- my main one, and one
which is a JPEG lib that is pointed to
from codeguru. I think its since I added that JPEG project into my stuff
that I sometimes (why not always?) get
the linker warning: LINK : warning LNK4098: defaultlib "LIBC" conflicts with use of other libs; use /NODEFAULTLIB:library
Of course, if I follow this advice and
put in the /NODEFAULTLIB I get a zillion
undefineds, so...
It may mean that something else is wrong
with my setup. However, I see no adverse effects -- everything seems to
work fine, so I've just been ignoring the warning, but now I'm getting ready to export my app, I'm wondering if I
should worry about this?? What do you
think?
has 2 projects -- my main one, and one
which is a JPEG lib that is pointed to
from codeguru. I think its since I added that JPEG project into my stuff
that I sometimes (why not always?) get
the linker warning: LINK : warning LNK4098: defaultlib "LIBC" conflicts with use of other libs; use /NODEFAULTLIB:library
Of course, if I follow this advice and
put in the /NODEFAULTLIB I get a zillion
undefineds, so...
It may mean that something else is wrong
with my setup. However, I see no adverse effects -- everything seems to
work fine, so I've just been ignoring the warning, but now I'm getting ready to export my app, I'm wondering if I
should worry about this?? What do you
think?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>it's not always safe to ignore this warning message.
Not always. But it is OK in this case. Am I right?
Not always. But it is OK in this case. Am I right?
> But it is OK in this case. Am I right?
There's no way to tell. But, odds are, it isn't. If you mix flavors of CRTL in the same image, you're most likely to get memory management problems.
tullhead used /NODEFAULTLIB and got lots of unresolved externals because he didn't bother to eplicitly name the CRTL version he wanted, and therefore all CRTL functions were unresolved.
..B ekiM
There's no way to tell. But, odds are, it isn't. If you mix flavors of CRTL in the same image, you're most likely to get memory management problems.
tullhead used /NODEFAULTLIB and got lots of unresolved externals because he didn't bother to eplicitly name the CRTL version he wanted, and therefore all CRTL functions were unresolved.
..B ekiM
..B ekiM