When I make a custom dll using NMake, and have a snoop inside using Dependency Walker, the libraries are bound to MSVCRxx.DLL.
The version appears to depend on the version of Visual Studio currently installed. E.g. the dlls that are in ia32/bin use MSVCR71.DLL and a custom dll that I create references MSVCR90.DLL (vs2008).
Is there a way for me to create custom dlls that statically link to the VC++ run-time libraries, or cleaner solution?
The reason that this is annoying is that it adds to the complexity of deployment scenarios :(
Any tips/thoughts??
Or have I lost the plot? :)
Ben
