The Linux version of the toolkit must be compiled from source code. The only requirement is the standard GNU/Linux toolchain consisting of make, gcc and ld. These are included with most Linux distributions but may require installation. On Debian™ based distributions, such as Ubuntu™, they may be installed using apt-get. On RedHat™ distributions, such as Fedora™, they may be installed using rpm. On SuSE™ based distributions, they may be installed using YaST2.
Example 1.1. Toolkit Installation on GNU/Linux™
# cp plc-utils-1.2.1.tar.gz /home/mydir # cd /home/mydir # tar -vzxf plc-utils-1.2.1.tar.gz # cd plc-utils-1.2.1 # make # make install # make manuals
Decompress the archive and extract the contents with the tar utility. This will create a folder having the same basename as the archive such that one version will not over-write another. Consult the tar man page on your system for detailed instructions. Change directory to the appropriate folder.
The main package folder contains a recursive Makefile that will compile and install all toolkit programs. If you do not want to compile and install all programs then change directory to the appropriate folder and run make from there. To compile binary files, type make. To install binary files, type make install. To install man pages, type make manuals. The package does not automatically install examples, scripts, applets or man pages.
We recommend that you login as root user before installing the toolkit; otherwise, you will be prompted for the root password as each program or component is installed.
Programs are installed in folder /usr/local/bin and man pages are installed in folders /usr/share/man/man1. If these folders are not correct for your system, or if you want to install in other folders, then edit the folder names defined in the make.def file found in main toolkit folder or over-ride these definitions in subordinate makefiles.
Toolkit web pages are not automatically installed. To access toolkit documentation, point your browser to docbook/index.html and add the page to the browser bookmark or favorites list. If you are interested in how the toolkit has been implemented then do the same for page docbook/toolkit.html.
The method described above is only recommended if you do not plan to move or remove toolkit folders. Otherwise, you can merely copy the entire contents of the toolkit docbook folder to another folder of your choice and point your browser to the new file locations.
cp -rv docbook/* /home/mydir/toolkit