On 2018-09-14 01:17, Erik Joelsson wrote:
I checked and the copying of java.exe was done in the now legacy jre
installer, so from what I can tell, there is no longer a need for
static linking.
Sounds good. I agree with your reasoning, it seems the main concern was
the copy to the system directory. A second point was raised in private,
that the old system of letting the java launcher select another version
to launch, could be behind this. Neither this system is kept anymore.
Thanks for all input!
/Magnus
/Erik
On 2018-09-13 09:14, Erik Joelsson wrote:
Hello,
Reading that bug, it seems the problem is when the installer copies
java.exe into the Windows system directory. In that case, it may not
have access to the msvcr re-distributables. I will try to find out if
our installers are still doing this.
/Erik
On 2018-09-13 06:32, Alan Bateman wrote:
On 13/09/2018 14:07, Magnus Ihse Bursie wrote:
:
Apparently, someone was trying to get rid of dll dependencies from
java.exe. Why that would be desirable it does not say. Neither why
this should not apply to all other launchers. (Perhaps there were
not that many in these days?)
Do anyone think this still seems relevant? Otherwise I'd like to
get rid of this hack, and link java and javaw just like all the
other launchers.
I don't know if it is still needed but it seems to be related to the
upgrade to VC 7 and an issue related to redistribution issue of the
MS runtime. JDK-6282039 and JDK-6382014 have some info on this.
-Alan.
