Mladen Turk wrote:
All higher MSVCRT versions has dependency on MSVCRT.dll so if you
build against that you have assurance that CRT functions will come
from the same CRT library regardless of the version used.
I know that stdio functions have problems, so if like mod_jk the
module uses them for logging or reading config files you might
get into trouble. We observed that with mod_jk and it manifested with
weired looking log files.
For example we use VS6 for building Tomcat Native, and it can
work in both JDK5 (compiled with VS6) and JDK6 (compiled with VS2003)
because it depends on MSVCRT.dll only.
In general MSVCRT.dll + MSVCRTxx.dll is OK, however
MSVCRTxx.dll + MSVCRTyy.dll is a very bad idea.
I just googled what it would take to get VS2005 to link against MSVCRT.dll.
It's doable, but not pretty at all.
I can see why you use VS6 to build stuff.
If only VS6 was still available on MSDN.
Thanks to both you and Rainer for filling in the blanks for me. And I
thought Linux glibc compatibility was confusing but this Microsoft
MSVCRT stuff makes glibc problems look easy to solve :)
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
