diff options
author | Andras Timar <atimar@suse.com> | 2013-05-21 03:43:52 -0700 |
---|---|---|
committer | Andras Timar <atimar@suse.com> | 2013-05-21 03:43:52 -0700 |
commit | b0a3cb212a2b53b2a6551b9c7f23355de7157e7c (patch) | |
tree | d89f741ec5652097e5cf5a2d490f7b652419f67e /oowintool | |
parent | 71101052ca31ef5da3700fdcf5540d22529d4ff2 (diff) |
make 64-bit shell extensions work, put 64-bit VC runtime in the same dir
Unlike in case of msvcr90.dll, which went to WinSxS, msvcr100.dll is installed
to the "system32" folder. Windows installer automatically replaces it to
SysWOW64. The problem is that this way 64-bit dlls end up in the wrong directory.
They conflict with the 32-bit dlls, and will not be installed. Therefore
64-bit shell extensions will not work, unless the 64-bit VC runtime is
installed from other source. It is not possible to install both 32-bit and
64-bit VC Runtime with merge modules in case of VS 2010 and VS 2012.
For the 64-bit shell extensions, we can install the runtime dlls next to the files.
Change-Id: I47060f8ff764ca1156596139ecbec003f964bc60
Diffstat (limited to 'oowintool')
-rwxr-xr-x | oowintool | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/oowintool b/oowintool index 26221f09c07e..6f5ab7cc52df 100755 --- a/oowintool +++ b/oowintool @@ -313,7 +313,7 @@ sub msvc_copy_dlls($$) my $srcdir = (cygpath ($ver->{'product_dir'}, 'w', 'u') . '/' . $ver->{'dll_path'}); - $srcdir =~ s/x86/amd64/ if ($arch eq 'amd64'); + $srcdir =~ s|/x86/|/x64/| if ($arch eq 'amd64'); copy_dll ($srcdir, "msvcp" . $ver->{'dll_suffix'} . ".dll", $dest . $ver->{'dll_suffix'}); |