Summary: | iconv.dll conflict on Windows 7 Outlook 2007 | ||
---|---|---|---|
Product: | [Applications] kleopatra | Reporter: | Bob <rchancer> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aheinecke, mutz |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | http://commits.kde.org/emerge/df962985fca2cae95b31974eb2972a3d934fd26f | Version Fixed In: | |
Sentry Crash Report: |
Description
Bob
2011-01-06 21:43:00 UTC
Hi, this is a "bug" in the application that installs iconv into c:\windows. GPG4Win is nice in the way that it does not put libraries into your PATH variable but only places the executable in there (the path is also used for library look up) as our libraries are no longer in the directory of our binary this leaves us vulnerable to Programs that place their libraries in the windows directory. I'll linkin bzip and and iconv static now. That should reduce some of the problems and fix this problem. Git commit df962985fca2cae95b31974eb2972a3d934fd26f by Andre Heinecke. Committed on 02/05/2013 at 13:04. Pushed by aheinecke into branch 'gpg4win'. Use a static version of winiconv. Winiconv is only linked by kdecore.dll so this might even reduce the size and additionally avoids library incompatibilities if evildoers installed iconv.dll into the system directory. M +1 -2 portage/win32libs/win_iconv/win_iconv-0.0.3.py http://commits.kde.org/emerge/df962985fca2cae95b31974eb2972a3d934fd26f |