[Pidgin] #7875: Pidgin should add Aspell location to its App Paths Windows registry entry

[Pidgin]

#7875: Pidgin should add Aspell location to its App Paths Windows registry entry
--------------------------+-------------------------------------------------
 Reporter:  dcitron       |        Owner:  datallah       
     Type:  defect        |       Status:  new            
Milestone:                |    Component:  winpidgin (gtk)
  Version:  2.5.3         |   Resolution:                 
 Keywords:  aspell crash  |  
--------------------------+-------------------------------------------------

Comment(by dcitron):

 Replying to [comment:1 rekkanoryo]:

 Thanks for considering this. Windows has a couple of mechanisms for
 dealing with this issue:
  1. App Paths
  1. [http://msdn.microsoft.com/en-us/library/ms684179(VS.85).aspx
 LoadLibraryEx] called with the full path to the DLL and the flag
 {{{LOAD_WITH_ALTERED_SEARCH_PATH}}}
  1. [http://msdn.microsoft.com/en-us/library/aa375193(VS.85).aspx Side-by-
 side assemblies]

 The solution I proposed initially worked for me on my particular
 installation. If that solution is rejected, then please consider instead
 implementing the second solution. I believe you are already reading the
 full path to the Aspell DLL from {{{HKLM\SOFTWARE\Aspell}}}, correct? If
 so, according to [http://msdn.microsoft.com/en-us/library/ms682586.aspx
 the documentation], calling:
 {{{
    LoadLibraryEx(pathFromAspellKey, NULL, otherFlags |
 LOAD_WITH_ALTERED_SEARCH_PATH);
 }}}
 should do the trick, no?

 Many operating systems have issues dealing with multiple versions of
 shared libraries. In my experience, LD_LIBRARY_PATH is hardly any better
 unless you set it per-application, and that's the same idea as App Paths.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/7875#comment:2>
Pidgin <http://pidgin.im>
Pidgin