I believe it builds a drag and drop app and is old tech. Py2app and bdist_mpkg are the modern ways to package Mac distorts (the latter for binary installers such as pygame).
What is the state of 1.9.2? I'm willing to try a binary distro when folks think it is time (though w/out pymidi alas since I cannot build it). Russell On Feb 19, 2012, at 6:15 AM, Zack Baker <zbaker1...@gmail.com> wrote: > Ok by three way I downloaded python 2.7.2 from pygame.org and whnen > downloaded had another application other than idle called 'build applet' with > what looks like a python script going through a scanner and an application > coming out on the other side(that is the icon) yet ive googled it and I > cannot seem to find anything to do with it. Also when I launch the app it > brings up a finder window for me tok chose a script but all the scripts are > greyest out. Any info would be great > > -Zack > > On Feb 18, 2012, at 8:32 AM, Enrico Kochon <ekoc...@uni-osnabrueck.de> wrote: > >> If Zack gets Pyinstaller to run on MacOs, this will be great! >> >> Struggling with py2app to the point were it run, was kind of driving me mad. >> >> >> Best regards >> >> Enno >> >> >> >> Am 18.02.2012 um 11:32 schrieb Sam Bull: >> >>> On Fri, 2012-02-17 at 16:44 -0500, Zack Baker wrote: >>>> So could you just resend an email with the command exactly how it would as >>>> oppear because that looks a littled funky. Let's assume that the game is >>>> called helloworld.py and put it in the trunk folder or wherever. Thank >>>> you! >>> >>> OK, if Pyinstaller were installed on your system you would run it with >>> "pyinstaller", but I haven't seen an installer for it. So, if you >>> download the release on their website, and extract it to the home >>> folder, you can run it with: >>> "python ~/pyinstaller-1.5.1/pyinstaller.py" >>> That is literally running the pyinstaller program in Python, much the >>> same as you would run your own Python program from the terminal. >>> >>> Adding "--onefile" ensures it compiles the files into a single binary. >>> >>> "-o foobar" tells it which folder to save the output to. So, this would >>> save it to the "foobar" folder inside whatever folder the terminal is >>> in. >>> >>> "spam/eggs.py" tells it the top-level file of your project (the one you >>> run to start the game). This would be the "eggs.py" file in the "spam" >>> folder inside whatever folder the terminal is in. >>> >>> So, if you have Pyinstaller extracted in your home folder and your >>> project is in the "trunk" folder, then this command should create a >>> single binary in a "pyinstaller/dist" folder. >>> >>> "python ~/pyinstaller-1.5.1/pyinstaller.py --onefile -o pyinstaller >>> trunk/helloworld.py" >>> >>> Assuming you've downloaded the same version, obviously change the >>> "pyinstaller-1.5.1" if that's not what the folder is called after >>> extraction. >>> >>> Oh, just remembered you may need to run this first, just once: >>> "python ~/pyinstaller-1.5.1/Configure.py" >>> >>> -- >>> Sam Bull <sambull.org> >>> PGP: 9626CE2B >>> >>