Thank you for your reply. There is indeed a manifest in python27.dll. Now I understand why things worked the way they did when I tried deleting my .exe.manifest file.
I suppose it would be a good idea to keep the .exe.manifest file, even though it's not an absolute necessity? (I would think there must be some good reason why PyInstaller creates it.) Also, I discovered that the reason py2exe could not embed icons into an EXE on my 64-bit system was because I was using the 32-bit version. I think it would work if I used the 64-bit version (with 64-bit Python). But then I would need to make separate 32-bit and 64-bit builds of my program, which I would prefer not to have to do. This is one of the reasons that I prefer to use PyInstaller. I was wondering, though, if in the future I wanted to build a 64-bit EXE, can PyInstaller do this? I understand the general differences between 32-bit and 64-bit, such as the different context menu DLLs required. But am I correct that there is no real advantage to using the 64-bit version of Python other than to be able to do complex mathematical calculations faster? (In case it makes a difference, my program has a wxPython GUI, it's not just a console program.) Thank you. On Monday, March 10, 2014 4:46:59 AM UTC-4, Martin Z wrote: > > On Saturday 08 of March 2014 11:42:31 Johnsons in DE wrote: > > I am not exactly sure how to do this with PyInstaller. I discovered that > > "[ProgramName].exe" will still run even if I delete the 4 MSVCRT files > in > > the application folder. I thought that I might need to modify the > > "[ProgramName].exe.manifest" file to point to the MSVCRT files in the > > subfolder of the Windows directory. However, I found the program still > ran > > even if I deleted that manifest file. > > > > Now I am somewhat confused. Is there a manifest embedded in the EXE > created > > by PyInstaller that will use the MSVCRT files in the Windows directory? > In > > other words, how can I accomplish what I want? Is it as simple as > deleting > > the MSVCRT files in the application folder? > > > > Thank you. > > I would have to chek but I think manifest is not embedded in the EXE > created > by PyInstaller. > > Could it be a manifest that is embedded inside any .dll file that gets > bundled? > > for example: python.dll? > > PyInstaller uses functions CreateActCtx / ActivateActCtx from the > windows api. These functions are related to manifest files and friends. > > They could give you insight how pyinstaller works. -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
