.There have been a few postings on LNK4099, for examples,
related to native libraries. A recent (March, 2013) rebuild of a Fotran static library with
Intel(R) Visual Fortran Composer XE 2011 Integration for Microsoft Visual Studio* 2010, 12.0.3470.2010
/nologo /debug:full /Od /warn:interfaces /names:uppercase /iface:stdref /module:"Debug\\" /object:"Debug\\" /Fd"Debug\vc100.pdb" /traceback /libs:static /threads /dbglibs /c
used by a C++ dll has given LNK4099 errors for each of the Fortran routines
staticlib.lib(*.obj) : warning LNK4099: pdb 'vc100.pdb' was not found with 'staticlib.lib(*.obj)' or at z:\path\vc100.pdb'; linking object as if no debug info
used by the dll
extern "C" void __stdcall *(...)
where * = name of subroutine.
Excluding the staticlib.lib is not an option. The Fortran settings (e.g. STDCALL, REFERENCE (/iface:stdref)) have not changed.
Making the debug version of staticlib.lib without debug gets rid of the link warnings but this defeats the purpose of a debug build.
The LNK4099 diagnostics are just warnings but any advice on getting a successful debug build without LNK4099 would be welcome.