Link warning question

[Patrick_Waugh]

I get the following warning:

LINK : warning LNK4098: defaultlib 'LIBC' conflicts with use of other libs; use /NODEFAULTLIB:library

and I'm using the LIBC.lib from the latest platform SDK. Using MS Visual Studio Pro, and just wondering if anyone knows of any library conflicts, or what I might check.

Patrick

[Pete Dowson]

LINK : warning LNK4098: defaultlib 'LIBC' conflicts with use of other libs; use /NODEFAULTLIB:library and I'm using the LIBC.lib from the latest platform SDK. Using MS Visual Studio Pro, and just wondering if anyone knows of any library conflicts, or what I might check.

I get that on some projects. Never found out why, and doing as it says ("NODEFAULTLIB") seems to make things worse. The warning doesn't seem to affect anything adversely so I learned to ignore it.

Since I upgraded to Visual Studio .NET 2005 it doesn't happen any more, but that's an expensive solution if, like me, you want/need the Pro version because of the superior optimisations. In fact, considering I only use the C/C++ Native code part, and of course the Debugger, the whole package is ridiculously expensive, but you can't get the good optimising compiler on its own any more. :-(

Regards,

Pete

[Patrick_Waugh]

Yes, I'm using 2005 as well, and I'm still getting it.

I'll play around with things and see if I can figure it out when I get some extra time.