-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b128
-
generic
-
generic
-
Verified
No one has a good explanation why in JDK6 we still
ship the old VC 6 msvcrt.dll alongside the msvcr71.dll in JDK.
Perhaps for convenience of some 3rd party JNI library that might have
been built against it and relied on our copy ?
Or perhaps because no one was able to be sure we weren't still using it.
I don't see any such use and as we upgrade to VS2010 and msvcr100.dll
we can't keep dragging along every older DLL at the same time, particularly
since each newer DLL is bigger than the last.
At least if we remove the 260K (or more?) of msvcrt.dll, it can compensate
for the size increase of msvcr100.dll over msvcr71.dll
ship the old VC 6 msvcrt.dll alongside the msvcr71.dll in JDK.
Perhaps for convenience of some 3rd party JNI library that might have
been built against it and relied on our copy ?
Or perhaps because no one was able to be sure we weren't still using it.
I don't see any such use and as we upgrade to VS2010 and msvcr100.dll
we can't keep dragging along every older DLL at the same time, particularly
since each newer DLL is bigger than the last.
At least if we remove the 260K (or more?) of msvcrt.dll, it can compensate
for the size increase of msvcr100.dll over msvcr71.dll
- relates to
-
JDK-7012519 JDK7 Built with on Windows with VS2010, will not be shipping msvcrt.dll, just msvcr100.dll
- Closed