Giovanni Bajo píše v Út 11. 01. 2011 v 11:30 +0100: > As for the embedded manifest in the executables, I don't know how it > gets there... can you please have a look? > > > While this doesn't lead to problems on my setup, it may > > be related to the R6034 error reported by others. Can we get rid of > the > > manifest in the bootloader? The only contents seem to be security > > options for Vista/Win7, which I could add to the manifest generated > by > > pyinstaller (I already added it to my local build, it was a trivial > > change, but I didn't commit yet). > > Yes, we can get rid of it, I don't think it should be generated in the > first place, and I don't know if it's useful or not. So, rather than > regenerating it from your patch, can you please check how it gets > added > to the executable? > > Maybe through the new build system? Martin?
The maanifest seems really getting there through the new build system. When using visual studio compiler, the manifest is always generated. Giovanni, could you please verify if MSVC 2003 uses lingflag /MANIFEST during compilation? You could get compilation details with using waf option -vv: python waf -vv build Part of waf code where manifest is handled: http://code.google.com/p/waf/source/browse/tags/waf-1.5.18/wafadmin/Tools/msvc.py?r=10833 Maybe other useful information: http://code.google.com/p/waf/issues/detail?id=595 Should I try to change the new build system to not embed manifest to bootloader? -- 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.
