After a bit of a struggle with PyInstaller (including trying to use output from Gui2EXE as a guide) I gave up and went back to square one and reconsidered my objectives - which were to try to see if I could get a smaller, single file executable for my project. I know PY2Exe works fine for my project (but creates a big folder with lots of files), so a bit of investigation showed that most of the smaller size of the PyInstaller output is due to the use of the UPX compression software, so I tried that on the py2exe output to see if I could manage as well as PYInstaller is reported to do. The results were interesting! If I used bundle_files (1 or 2) to get less files UPX could get considerable compression on everything except my main exe file which it could do little for - I only dropped my total project size from about 28Mb to 26Mb - and probably with most savings in those dlls included like msvcr71.dll which I possibly don't need anyway. If I didn't bundle files I did a lot better (even with my main exe file), and got the lot down to about 16Mb - good, but still a long way short of my Inno installer compressed installation file which is under 7Mb. I am now looking at an article on the py2exe web-site which suggests that it is possible to use NSIS instead of Inno Setup to create a single file compressed executable which when executed will uncompress into a temporary folder and run. When the application exits the temp folder is deleted automatically. Obviously the main question is 'how big is the load time when starting the app'. I'll let you know how I go!
Roger --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
