> No, it doesn't. Anyhow I used google to find some information
> about it and I think that some advanced MSVC users should look
> at it and answer what will happen when Harbour is build for
> different MSVCRT then one of used DLLs when /MT or /MD switches
> are used (it may exploit some problems with 3-rd party harbour
> binaries) and maybe which switches are present in some old MSVC
> versions.
> Anyhow I'm not MSVC users and I cannot help here so I'm leaving
> this problem to people using this compiler.

Here is some MS docs:
   http://msdn.microsoft.com/en-us/library/2kzt1wy3(VS.80).aspx

With MSVC 2008 there is NO difference between no option 
and /MT, and '_MT' macro is always defined. This means in 2008, 
MT mode is always enabled. Slightly different code is generated 
with /MD and /MDd, and 

--- test.bat
call vc cl -I..\..\include -c hbstr.c      -FoM__
rem   _MT defined, links to LIBCMT.lib

call vc cl -I..\..\include -c hbstr.c -MT  -FoMT_
rem   _MT defined, links to LIBCMT.lib

call vc cl -I..\..\include -c hbstr.c -MTd -FoMTd
rem   _MT defined, links to LIBCMTD.lib

call vc cl -I..\..\include -c hbstr.c -MD  -FoMD_
rem   _MT defined, links to MSVCRT.lib

call vc cl -I..\..\include -c hbstr.c -MDd -FoMDd
rem   _MT defined, links to MSVCRTD.lib
---

This should be checked for older versions, 2005 and 
maybe .NET 2003, .NET, maybe 6.0 if someone still 
has it.

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to