Just a quick update, I've started working on some patches which should fix assembly dependencies on windows in general. I think I may be ready in a few days. My current outline of changes:
- add manifest embedding/extraction support to pyinstaller (manifest.py - provides UpdateManifest and GetManifest methods). Status: 50% done. - add general resource embedding/extraction support to pyinstaller (resource.py - provides AddResource and GetResource methods, used by manifest.py). Status: 50% done. - add manifest query code to bindepend.py, to look inside binary dependencies, extract the manifest if any, get the dependant assemblies if any by looking at the manifest and searching for the assembly in WinSxS folder, then adding the assembly files as BINARY. Status: just started working on it. On 14 Mrz., 16:36, Florian Höch <[email protected]> wrote: > Yes, I agree that it doesn't make much sense to fix it in pyinstaller > if it's going to be fixed (hopefully ;)) in python itself anyway. > > Regarding your question: No, unfortunately the manifest seems to be > needed, otherwise the exe will show an error popup right after launch > ('application configuration incorrect') and close. > > On 14 Mrz., 14:53, Giovanni Bajo <[email protected]> wrote: > > > On ven, 2009-03-13 at 04:47 -0700, Florian Höch wrote: > > > > Thanks, now I found what I was missing - the executable also needs an > > > updated manifest which references the CRT. Then, it also works with > > > Python 2.6.1 (for Python 2.6 the changed manifest is not needed) > > > Summary so far for me: > > > > - My method above: works with Python 2.6 (both --onedir and -- > > > onefile), --onedir also works with Python 2.6.1, but not --onefile > > > - My method above + assembly next to the executable (DLLs + > > > Microsoft.VC90.CRT.manifest, either in subfolder called > > > Microsoft.VC90.CRT or loose files): --onefile also works with Python > > > 2.6.1 (even though it is no longer really a onefile deployment - but I > > > certainly don't blame pyinstaller) > > > > I also found thishttp://bugs.python.org/issue4566Ididn't know about > > > before - so maybe we can hope that a real fix for those issues will be > > > incorporated into Python itself in a next version. > > >From the reading of the bug, I deduce that the executable's manifest is > > > not required anymore in Python 2.6.2. This will leave Python 2.6.1 as > > the only version requiring this workaround -- in which case, I prefer to > > simply declare it unsupported and bail out when running Configure.py > > against it. > > > On the other hand, I would like to incorporate your fixes for Python 2.6 > > but we need to find a better way of doing it. > > > First question: if you *don't* add the msvc*90.dll and the manifest to > > the a.binaries list, but you simply copy them like this: > > > YourProgram.exe <- made by PyInstaller > > Microsoft.VC90.CRT\ > > msvcr90.dll > > msvcp90.dll > > etc. > > > so *without* copying the manifest, does it work? > > -- > > Giovanni Bajo > > Develer S.r.l.http://www.develer.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
