Ah, I'd tried the assembly's manifest. Unfortunately when I updated the plugins with winmanifest.py and the manifest you provided, the plugins broke again. I tried adding a combination of the MS manifest file and DLLs back to the directory, but that didn't help. I checked that the version number and key token match the DLLs and manifest file.
On Tue, Feb 22, 2011 at 8:53 PM, Florian Höch <[email protected]> wrote: > Hi, > > thanks for trying that out. The problems you are seeing could be related to > the manifest contents you've added to the dll's. Did they look like this > (crossing my fingers the XML won't be mangled by the list): > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1"> > <assemblyIdentity name="nameIsInformative" processorArchitecture="x86" > type="win32" version="1.0.0.0"/> > <dependency> > <dependentAssembly> > <assemblyIdentity name="Microsoft.VC90.CRT" processorArchitecture="x86" > publicKeyToken="1fc8b3b9a1e18e3b" type="win32" version="9.0.21022.8"/> > </dependentAssembly> > </dependency> > </assembly> > > Reason I'm asking is because I forgot to point out that the actual > assembly's manifest (e.g. Microsoft.VC90.CRT.manifest) won't work for this > case, as it describes the assembly itself, not a dependency on it like the > above one (I hope I'm making sense). > > Regards > > Am 20.02.2011 21:39, schrieb Damien Elmes: >> >> I tried running winmanifest.py but didn't have any luck, so I tried >> also putting extra files in the qt4_plugins/imageformats directory: >> >> wm.py + Microsoft...manifest: still broken >> wm.py + msvc*.dll: crash >> wm.py + MS...manifest + msvc*.dll: problem fixed >> >> So it appears by distributing an extra copy of the DLLs I can work >> around the problem. It would be nice not to have to do that, >> especially since people who need the Qt4 codecs or DB modules will >> have to copy the DLLs to those dirs too, but at least the initial >> problem is solved for now. >> >> Cheers, >> Damien >> >> On Sun, Feb 20, 2011 at 11:54 PM, Florian Höch<[email protected]> >> wrote: >>> >>> Hi, >>> >>> Am 20.02.2011 06:25, schrieb Damien Elmes: >>>> >>>> Hi folks, >>>> >>>> I have users who don't have vcredist installed reporting that images >>>> are failing to show up, and once they install it the images appear >>>> correctly. My guess is that the manifest altering step than >>>> pyinstaller goes through doesn't extend to the plugin copying. >>> >>> Currently the code only fixes pyd's, but could be more or less easily >>> extended to also process dll's, although it would require a bit work so >>> it >>> doesn't pick up assembly dll's. >>> >>>> Until there's a fix for this, would running winmanifest.py<plugin> >>>> Microsoft.VC90.CRT.manifest be sufficient to work around this? >>> >>> Yes, it should, please try that and report back. Thanks! >>> >>> Regards >>> -- >>> 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. >>> >>> >> > > -- > 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. > > -- 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.
