>> depending on the permissions of the user who ran the installation.
>> just make it always work relative to the pidgin dll.
>> starts picking up things out of the installed version.
> others (Gtk) seems to not. We can protect all of them in the same way.
Hmm... Gtk doesn't appear to be treated differently.
The cases we've been talking about involve dynamic loading (LoadLibrary).
Gtk and friends are linked directly and not explicitly dynamically loaded.
that the Gtk/bin directory is preferred.
>> reason) that we ship old versions of some of those dependencies.
>> broken in various ways.
> reason for sticking with last secure version.
>>> updates (as I said above). I can implement it also.
>> necessary.  This may be a lot of work though.
> I think, this is actually the best idea. Clean and efficient.
> versions but security fixes and features that we actually could use.
I agree that we don't need to treat Gtk differently (as such).
it for that reason anymore.
> hours after my request.
Cool, it's good to hear that he's been so responsive.
>> - the source is in the zip file.
>> source is here: https://hg.pidgin.im/util/drmingw/.
compile these as part of the Pidgin packaging process?
downloaded as part of the build environment being set up.