| followed by the appropriate arguments. You should of course substitute the |
followed by the appropriate arguments. You should of course substitute the |
| correct path to your Python installation's "scripts" directory. |
correct path to your Python installation's "scripts" directory. |
| |
|
| |
The 'peak' script is designed for use as a '#!' command interpreter for |
| |
certain file types, such as ZConfig configuration files. Some Unixes, |
| |
however, do not support using scripts as '#!' interpreters. To work around |
| |
this, there is a (currently experimental) 'invoke' program you can build. To |
| |
build the 'invoke' program, go to the directory you unpacked the PEAK source |
| |
in, and type:: |
| |
|
| |
gcc -o invoke scripts/invoke.c |
| |
|
| |
This will build an 'invoke' executable, which you can then place on your |
| |
system's path or other appropriate location. You can then use '#!' lines |
| |
like this (replacing '/usr/local/bin' with the directory where you installed |
| |
'invoke', of course):: |
| |
|
| |
#!/usr/local/bin/invoke peak EventDriven |
| |
...rest of config file goes here |
| |
|
| |
'invoke' allows an arbitrary number of space-separated arguments to be passed |
| |
to the command it invokes, thus working around various Unixes' '#!' parsing |
| |
problems, as well as the "can't use a script as an interpreter" problem. It |
| |
also searches the system PATH for the specified command. You may find this |
| |
useful for non-PEAK script interpreters as well. |
| |
|
| |
|
| |
|
| TESTING YOUR INSTALLATION |
TESTING YOUR INSTALLATION |
| |
|
| python C:\Python22\Scripts\peak test |
python C:\Python22\Scripts\peak test |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| THIRD PARTY SOFTWARE INCLUDED WITH PEAK |
THIRD PARTY SOFTWARE INCLUDED WITH PEAK |
| |
|
| Aaron Watters' 'kjbuckets' Module |
Aaron Watters' 'kjbuckets' Module |
Diff of /PEAK/INSTALL.txt
Parent Directory
| 
Revision Log