On Mon, 2011-01-10 at 21:26 +0100, Florian Höch wrote: > Hi Giovanni, > > I noticed that the bootloader executables contain a manifest as resource > since some time (I don't know since when, but some of my older exe's do > not contain it).
Hi Florian, there is a 0-byte manifest.xml in source/windows; I messed up with it, it should have been removed after your patch (after the manifest is generated by Build.py). 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? -- Giovanni Bajo :: [email protected] Develer S.r.l. :: http://www.develer.com My Blog: http://giovanni.bajo.it Last post: Compile-time Function Execution in D -- 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.
