Hi Giovanni,
I've not yet looked into it, I'll keep you posted when I get to it.
Adding our own manifest to the Pyinstaller generated exe should be no
problem (code is still there in the py26win branch to handle it, it's
just not used by default currently); I just fear it could have
implications for onefile exe's.
Am 21.04.2010 02:43, schrieb Giovanni Bajo:
Hi Florian,
is it possible that py26win branch was broken by Python 2.6.5? Importing
.pyd files (compiled by myself through distutils) from within a packaged
executable fails with a "DLL load failed" error. It looks related to this
patch:
http://svn.python.org/view/python/trunk/Lib/distutils/msvc9compiler.py?r1=76651&r2=76650&pathrev=76651
that was added in 2.6.5. I believe it now fails because we don't use
Python.exe but our own .exe, which does not have a manifest.
Does any of this make sense to you?
(PS: and how MS managed to recreate the DLL hell after the problem had
eventually settled down? :) )
(PS: couldn't agree more :) )
--
Florian Höch
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
