Rainer Jung wrote:
Mladen might like to elaborate more, but in short: MS binaries need a
Microsoft Visual C++ Runtime library to run with. Those are called
msvcrt. The library version used is determined during the dynamic
linking done with visual studio.
Now if you use an extensible application like Apache, and the web server
and the modules you want to load are compiled with different Visual
Studio versions, multiple and possibly incompatible version of the
msvcrt libs will be loaded during runtime.
Until now, the official downloads of the Apache web server are compiled
with VS6, so our mod_jk Windows binaries are also compiled with VS6 in
order to circumvent possible havoc.
I did see mod_jk compiled with newer VS version running in the standard
Windows Apache from the web server download page, but you *might* run
into trouble.
Regards,
Rainer
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?
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.
Thanks,
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
