| Jack Jansen | 0511b76 | 2001-09-06 16:36:42 +0000 | [diff] [blame^] | 1 | This directory contains a Makefile that will create a proof-of-concept |
| 2 | Mac OS X application for Python. The process is far from streamlined, |
| 3 | and it will definitely change in future releases of Python, but I wanted to |
| 4 | include this in the current distribution so people could play with it. |
| 5 | |
| 6 | To create a fullblown Python.app proceed as follows. |
| 7 | |
| 8 | 1. In the main Python source directory configure python with |
| 9 | configure --enable-framework --with-suffix |
| 10 | 2. Do a "make clean" if you did a previous build, then "make". |
| 11 | 3. Install this as a framework with "make frameworkinstall". This puts a Python |
| 12 | framework into /Library/Frameworks. |
| 13 | 4. Come back here (Mac/OSX) and build and install the application, |
| 14 | with "make install". |
| 15 | 5. It is probably a good idea to add the Mac-specific modules to the framework, |
| 16 | with "make installmacsubtree". This puts a MacPython lib directory into |
| 17 | sys.prefix/Mac/Lib. Again, this is a temporary measure. |
| 18 | |
| 19 | You are now done. In your Applications you should have a "Python", with the icon |
| 20 | being a falling 16 Ton weight with a shadow under it. You can drop Python scripts |
| 21 | on this and the will be run, in a full-windowing environment. Note that you |
| 22 | do not get sys.stdin, and that sys.stdout goes to the console (Use |
| 23 | Applications/Utilities/Console to see it). |
| 24 | |
| 25 | Something to take note of is that the ".rsrc" files in the distribution are not |
| 26 | actually resource files, they're AppleSingle encoded resource files. |
| 27 | |
| 28 | Jack Jansen, jack@oratrix.com, 6-Sep-01. |