From: Werner F. B. <wer...@fr...> - 2010-03-15 07:48:55
|
On 15/03/2010 01:39, Daryl Tester wrote: > Josh English wrote: > >> I have them in the same folder as my executable. > > Ah, my bad - I was thinking you couldn't run the exe on your > destination system. All comments below are in the context of > not being able to run the exe on the system you're compiling > it on. > >> There's nothing about >> them in the setup.py script, so I hand copied them. > > There shouldn't be any mention of them in the setup script. And you > shouldn't need to copy them in manually either; my build script > removes the build/& dist/ directories so that they're rebuilt from > scratch for each compile (i.e. I believe py2exe is supposed to locate > the appropriate DLL and copy that into dist/ for you). > >> It's my (probably mis-)understanding that I need the same MZVCR**.dll >> files that Python was compiled with, and for me I think thats >> MSVCR90.dll version 9.0.21022.8. > > Yes. And I believe if you're running on anything more recent than XP > (i.e. Vista, Windows 7) then other issues come into play wrt assemblies > and manifests and tigers, oh my. I don't know how well py2exe copes > with this as this is an environment I haven't had to play in yet. It works very well. I dev on Windows 7 and deploy to Win 7, Vista, XP, Win 2000 without any problem. However I do not use bundle-file=1 or 2 only 3! With Python 2.6 you need to copy/install the sxs stuff yourself, a setup.py which works for me with Py 2.6 and wxPython 2.8.10 can be seen here. http://wiki.wxpython.org/py2exe Werner |