"Mark Tolonen" said :
> Yes, welcome to Microsoft's solution to DLL Hell...Side-by-Side DLL
> Hell.
As always, it boils down to a philosophical choice : is it better to suffer
through Hell alone, or in bad company ? :-)
--
http://mail.python.org/mailman/listinfo/python-list
"Fred Pacquier" wrote in message
news:xns9ca8b91a1519apacmanr...@212.27.60.38...
After installing the MS redistributable DLL package -- actually I had to
install *three* before hitting the right one (2005SP1) -- libpyexiv2
finally loads all its dependencies.
Of course I've still no idea why/
Fred P said :
> Hi, a bit of platform-specific advice sought here... I'm trying to
> diagnose one of those mysteries Windows is so fond of...
> Say that I have code that imports some binary Python module from site-
> packages (in this case, libpyexiv2.pyd through pyexiv2.py, could be
> anythng els
"Mark Tolonen" said :
> That error message is returned from executables built with later
> versions of Visual Studio (at least 2005 and 2008...not sure about
> 2003). The Windows application event log will indicate what DLL is
> missing.
>
> In addition to tools others have noted, depends.exe
"Fred P" wrote in message
news:xns9ca5e52bec783pacmanr...@212.27.60.39...
Hi, a bit of platform-specific advice sought here... I'm trying to
diagnose
one of those mysteries Windows is so fond of...
Say that I have code that imports some binary Python module from site-
packages (in this case,
Christian Heimes said :
> Fred P wrote:
>> Is there any tool and/or methodology I could use to at least pinpoint
>> the exact DLL that libpyexiv2 is failing to load, and ideally also
>> the reason why ?...
>
> The depencency walker http://www.dependencywalker.com/ works fine for
> me.
I'd neve
Fred P wrote:
> Is there any tool and/or methodology I could use to at least pinpoint the
> exact DLL that libpyexiv2 is failing to load, and ideally also the reason
> why ?...
The depencency walker http://www.dependencywalker.com/ works fine for me.
Christian
--
http://mail.python.org/mailma
Hi, a bit of platform-specific advice sought here... I'm trying to diagnose
one of those mysteries Windows is so fond of...
Say that I have code that imports some binary Python module from site-
packages (in this case, libpyexiv2.pyd through pyexiv2.py, could be anythng
else).
On three Windows
