On mar, 2011-01-11 at 21:33 +0100, Florian Höch wrote: > Am 11.01.2011 19:45, schrieb Stefan Fruehwirth: > > On 11 Jan., 16:53, Giovanni Bajo<[email protected]> wrote: > > > >> Another test: change your program so that it prints > >> os.environ["_MEIPASS2"] and doesn't exit immediately; then, while it is > >> running, go to the temporary directory that was printed and check if the > >> manifest file is there. > > > > Yep, same content. Strange. I'm starting to think that my system is > > messed up. Although I have experienced no troubles elswhere :-/ > > Hmm, maybe, but I somehow doubt it :) My bets are currently on getting > rid of the redundant manifest resource in the bootloader, hoping that > this will already be enough to eventually fix the problem (it could be a > race condition between WinSxS automatically grabbing the manifest > resource, thus somehow blocking pyinstaller's own attempt at loading the > correct manifest. But that's really just my speculation at the moment).
I've just committed an updated bootloader in SVN trunk (thanks to Martin for disabling manifest generation), for Windows 32-bit. Stefan, can you please try again with SVN trunk? (assuming you are not using 64-bit Python on 64-bit Windows) -- Giovanni Bajo :: Develer S.r.l. [email protected] :: http://www.develer.com 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.
