| 1 | ; Script generated by the Inno Setup Script Wizard.
|
|---|
| 2 | ; SEE THE DOCUMENTATION FOR DETAILS ON CREATING INNO SETUP SCRIPT FILES!
|
|---|
| 3 |
|
|---|
| 4 | ; This is the whole ball of wax for an Inno installer for Python.
|
|---|
| 5 | ; To use, download Inno Setup from http://www.jrsoftware.org/isdl.htm/,
|
|---|
| 6 | ; install it, and double-click on this file. That launches the Inno
|
|---|
| 7 | ; script compiler. The GUI is extemely simple, and has only one button
|
|---|
| 8 | ; you may not recognize instantly: click it. You're done. It builds
|
|---|
| 9 | ; the installer into PCBuild/Python-2.2a1.exe. Size and speed of the
|
|---|
| 10 | ; installer are competitive with the Wise installer; Inno uninstall
|
|---|
| 11 | ; seems much quicker than Wise (but also feebler, and the uninstall
|
|---|
| 12 | ; log is in some un(human)readable binary format).
|
|---|
| 13 | ;
|
|---|
| 14 | ; What's Done
|
|---|
| 15 | ; -----------
|
|---|
| 16 | ; All the usual Windows Python files are installed by this now.
|
|---|
| 17 | ; All the usual Windows Python Start menu entries are created and
|
|---|
| 18 | ; work fine.
|
|---|
| 19 | ; .py, .pyw, .pyc and .pyo extensions are registered.
|
|---|
| 20 | ; PROBLEM: Inno uninstall does not restore their previous registry
|
|---|
| 21 | ; associations (if any). Wise did. This will make life
|
|---|
| 22 | ; difficult for alpha (etc) testers.
|
|---|
| 23 | ; The Python install is fully functional for "typical" uses.
|
|---|
| 24 | ;
|
|---|
| 25 | ; What's Not Done
|
|---|
| 26 | ; ---------------
|
|---|
| 27 | ; None of "Mark Hammond's" registry entries are written.
|
|---|
| 28 | ; No installation of files is done into the system dir:
|
|---|
| 29 | ; The MS DLLs aren't handled at all by this yet.
|
|---|
| 30 | ; Python22.dll is unpacked into the main Python dir.
|
|---|
| 31 | ;
|
|---|
| 32 | ; Inno can't do different things on NT/2000 depending on whether the user
|
|---|
| 33 | ; has Admin privileges, so I don't know how to "solve" either of those,
|
|---|
| 34 | ; short of building two installers (one *requiring* Admin privs, the
|
|---|
| 35 | ; other not doing anything that needs Admin privs).
|
|---|
| 36 | ;
|
|---|
| 37 | ; Inno has no concept of variables, so lots of lines in this file need
|
|---|
| 38 | ; to be fiddled by hand across releases. Simplest way out: stick this
|
|---|
| 39 | ; file in a giant triple-quoted r-string (note that backslashes are
|
|---|
| 40 | ; required all over the place here -- forward slashes DON'T WORK in
|
|---|
| 41 | ; Inno), and use %(yadda)s string interpolation to do substitutions; i.e.,
|
|---|
| 42 | ; write a very simple Python program to *produce* this script.
|
|---|
| 43 |
|
|---|
| 44 | [Setup]
|
|---|
| 45 | AppName=Python and combined Win32 Extensions
|
|---|
|
|---|
