-
Enhancement
-
Resolution: Fixed
-
P2
-
6
-
b33
-
x86
-
windows
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2199009 | 7 | Andy Herrick | P2 | Resolved | Fixed | b64 |
mustang b63.
currently deploytk.dll and npdeploytk.dll dynamically link to msvcr71.dll. you can use the dumpbin /IMPORTS command to check the dependency.
if you try to deploy these dll to a machine that does not have msvcr71.dll, deploytoolkit won't work.
this prevent deploying the toolkit standalone.
to fix this, one way is to statically link to the crt library instead (use -MT)
i think we can just set MS_RUNTIME_STATIC to true in the toolkit make files to do that
currently deploytk.dll and npdeploytk.dll dynamically link to msvcr71.dll. you can use the dumpbin /IMPORTS command to check the dependency.
if you try to deploy these dll to a machine that does not have msvcr71.dll, deploytoolkit won't work.
this prevent deploying the toolkit standalone.
to fix this, one way is to statically link to the crt library instead (use -MT)
i think we can just set MS_RUNTIME_STATIC to true in the toolkit make files to do that
- backported by
-
JDK-2199009 deploytk.dll and npdeploytk.dll dynamically link to msvcr71.dll
-
- Resolved
-