Andy Wang wrote:
Rainer Jung wrote:
Ahh. I see, I think maybe I was misunderstanding Mladen then. I
thought that just building with VS2005 would result in some level of
multiple msvcrt library confusion.
If, we build our own Apache, and our own mod_jk, and our own everything
else up the toolchain (zlib, openssl, etc etc), we shouldn't have
problems with multiple msvcrt dependencies right?
Exactly.
But, that brings up a really interesting point, considering that our
customers may have their own modules and who knows how they build them.
I'll have to consider that.
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.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
