On Jun 27, 2006, at 11:51 PM, Marc Hedlund wrote: > > I just did my first build of a Python app using the Universal > Python 2.4.3 > package, py2app-0.2.5-py2.4-macosx10.4.zip, > wxPython2.6-osx-unicode-2.6.3.2rc2-universal10.4-py2.4.dmg, and > pycrypto-2.0.1_py2.4.zip (which I found in the "Kitchen Sink" > package at > <http://twistedmatrix.com/trac/wiki/Packages>). > > The resulting binary built on the first try, which is great. > However, it > went from 11.5 Megs (previous build on Mac/Intel, using 2.4.1 and > non-universal packages) to about 16 Megs. Is that about par for the > course? Any suggestions for paring it down? (The same binary on > Windows/py2exe is about 5.5 Megs.)
It's expected that a universal build should be roughly 2x the code size. You're not going to pare it down very much, but compression solves most of these problems because there's a lot of redundancy. You should really only be looking at the zipped or dmg'ed size of the executable. -bob _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
