MT runtime library

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In the file settings for one of the .cpp files in a Win32 unmanaged DLL project, the runtime library it is using by default is Multithreaded Debug. Is there any point in using multithreaded library if it isn't multithreaded DLL? Or does it need this to support multiple clients at once?
There isn't any COM involved

Thanks.
 
In the file settings for one of the .cpp files in a Win32 unmanaged DLL project, the runtime library it is using by default is Multithreaded Debug. Is there any point in using multithreaded library if it isn't multithreaded DLL? Or does it need this to support multiple clients at once?
There isn't any COM involved.
Click to expand...

If your application doesn't use multiple threads, there's no need for
it to use the multi-threaded library. However, unless you have any
strict performance requirements, you might as well stick with the
multi-threaded library.

Dave
 
project, the runtime library it is using by default is Multithreaded Debug.
Is there any point in using multithreaded library if it isn't multithreaded
DLL? Or does it need this to support multiple clients at once?
If your application doesn't use multiple threads, there's no need for
it to use the multi-threaded library. However, unless you have any
strict performance requirements, you might as well stick with the
multi-threaded library.
Click to expand...

What if your DLL is ever going to be used by an MFC application via the
DLL's lib file?

Thanks,

Jeff F
 
It's never going to be used by anything other than the exported function.
And probably only ever by one app.
 
What if your DLL is ever going to be used by an MFC application via the
DLL's lib file?
Click to expand...

MFC apps have needed to use the MT library for some versions now, but
the basic rule of thumb is that if the DLL will be used in a MT
situation, then it's wise to use the MT run-time.

Dave
 
Back
Top