Requirements
The developer tools require a Java Runtime Environment, version 1.5 or higher. A suitable runtime is available from Sun Microsystems at http://java.sun.com/j2se/1.5.0/download.jsp
. Make sure you set the value of the JAVA_HOME environment variable to the directory where Java is installed, and add the java binary to your PATH.
Obtaining Packages
Developer tools packages are available from the zutubi website
. Packages are available in three formats:
| Format |
Description |
| exe |
Executable Windows installer. |
| tgz |
Compressed tar archives. |
| zip |
Zip archives. |
Any of the formats may be installed on Windows systems. The tar archives are recommended for Unix-like systems, as the tar format has standard support for Unix-style file permissions.
Packages have names of the form:
where <version> is the version of pulse™ and <type> is an extension from the types described above.
Installation
Windows Installer
To install on a Windows system, execute the installer and follow the instructions. When the installation is complete, continue at the next step (Adding the Tools to the Path).
Archives
The tar and zip archives may be installed anywhere on the host system by unpacking the archive. All archives unpack to a directory of the same name as the archive, excepting the extension. For example:
The directory that the archive expands to is known as the pulse™ home directory. So that the developer tools can locate the home directory, you need to set an environment vairable PULSE_HOME to the absolute path of that directory. Continuing the example above, assuming a bash-like shell:
So that this variable is always set, you should add the directive above to your profile or your shell's rc file. Windows users can add the variable using the Control Panel (Start > Control Panel > System > Advanced > Environment Variables).
Adding the Developer Tools to the Path
The pulse™ developer tools are controlled from a single script, pulse (pulse.bat on Windows). This script is located in the directory $PULSE_HOME/bin. Although the script may be run directly from that location, it is more convenient to add it to your PATH so that it is always accessible. For example, using a bash-like shell, you could add the following to your profile:
Windows users can modify the system PATH using the Control Panel (Start > Control Panel > System > Advanced > Environment Variables).