

  PECOMATO - INSTALLATION
  =======================


	GNU/Linux installation
	======================

Available packages for GNU/Linux systems:

 - sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
   be used if unzip and unrar are installed).

 - binary archives for glibc 2.2 x86 32bit, successfully tested on RedHat 7.0
   to 9, RHEL 2.1 to 3, Fedora Core 1 and 2, SuSE 7.1 to 9.1, Mandrake 10.x.
   Other distros are untested yet.

 - binary archives for glibc 2.4 x86 32bit, successfully tested on FC5.
   Other distros are still untested.

 - binary RPMs and sources RPM built on RH7 (glibc 2.2 x86 32bit) and FC5
   (glibc 2.4 x86 32bit), those packages have no distro-specific dependencies
   excepted the glibc, so they can be used on other rpm-based systems.


		Installing from the sources
		===========================

Pre-requisites: installing pecomato from the sources requires a common
GNU/Linux system to be configured, including the traditional toolchain for
ANSI C development (GNU make 3.79, gcc, binutils, etc.). Python 1.5 mininum is
required to generate the documentation. Perl 5 minimum and CVS access are
necessary to build the sources archives (for packagers).

Unpack the sources archive, enter the sources directory then:


  $ make -f Makefile.linux
  $ make -f Makefile.linux install


This will install all files in dist-linux/, it's up to you to install the
binary and doc files to your user's home or to a system-wide location (as
root), preferably so that pecomato binary is found on all users' PATH.


		Installing from a binary archive
		================================

Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH, as root or not according to your
permissions or wishes.


		Installing from a RPM
		=====================

Prefer RPMs if your system is RPM-based and a RPM is available for your distro.


  $ rpm -ivh filename.rpm


or to upgrade an already existing version:


  $ rpm -Uvh filename.rpm



	Unix installation
	=================

Available packages for Unix systems:

 - sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
   be used if unzip and unrar are installed).

 - binary archives for IBM Aix 4.3.3 32bit to Aix 5.3 32bit.

 - binary archives for FreeBSD 5.4 i386 32bit. FreeBSD port is also available.

 - binary archives for HP-UX 11.00 32bit to HP-UX 11.11 32bit.

 - binary archives for HP-UX 11.23 64bit (Itanium2).

 - binary archives for Sun Solaris 2.6 SPARC 32bit (SunOS 5.6) to Solaris 8
   SPARC 32bit (SunOS 5.8).

 - binary archives for Sun Solaris 10 Intel (SunOS 5.10 i386 32bit).

 - binary archives for GNU/Solaris Nexenta (SunOS 5.11 i386 32bit).


		FreeBSD specific notes
		======================

pecomato is available from the ports collection of FreeBSD. Make sure that
the ports are installed on your FreeBSD system, then:


  $ cd /usr/ports/graphics/pecomato
  $ make install distclean


pecomato is known to compile on FreeBSD 5.4 up to 7.0, with either gcc 3.x or
gcc 4.x, x86 and amd64.

Other than that, you can install pecomato from the sources or from the
available binary package, see below.


		Installing from the sources
		===========================

Pre-requisites: installing pecomato from the sources requires the GNU ANSI C
compiler to be installed (gcc), other traditional development tools are
required (GNU make 3.79, binutils). Python 1.5 mininum is required to generate
the documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers).

Unpack the sources archive, enter the sources directory then:


  $ make -f Makefile.unix
  $ make -f Makefile.unix install


This will install all files in dist-unix/, it's up to you to install the
binary and doc files to your user's home or to a system-wide location (as
root), preferably so that pecomato binary is found on all users' PATH.


		Installing from a binary archive
		================================

Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH, as root or not according to your
permissions or wishes.


	QNX installation
	================

Available packages for QNX systems:

 - sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
   be used if unzip and unrar are installed).

 - binary archives for QNX 6.3.0 x86 32bit.


		Installing from the sources
		===========================

Pre-requisites: installing pecomato from the sources requires the GNU ANSI C
compiler to be installed (gcc), other traditional development tools are
required (GNU make 3.79, binutils). Python 1.5 mininum is required to generate
the documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers).

Unpack the sources archive, enter the sources directory then:


  $ make -f Makefile.qnx
  $ make -f Makefile.qnx install


This will install all files in dist-qnx/, it's up to you to install the
binary and doc files to your user's home or to a system-wide location (as
root), preferably so that pecomato binary is found on all users' PATH.


		Installing from a binary archive
		================================

Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH, as root or not according to your
permissions or wishes.


	BeOS installation
	=================

Available packages for BeOS systems:

 - sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
   be used if unzip and unrar are installed).

 - binary archive for BeOS Commercial/Personal Editions 5.0.3 x86 32bit.

 - binary packages for BeOS Commercial/Personal Editions 5.0.3 x86 32bit, as
   well as a .pkg and a .sea.


		Installing from the sources
		===========================

Pre-requisites: installing pecomato from the sources requires the GNU ANSI C
compiler to be installed (gcc), other traditional development tools are
required (GNU make 3.79, binutils). Python 1.5 mininum is required to generate
the documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers).

Unpack the sources archive, enter the sources directory then:


  $ make -f Makefile.beos
  $ make -f Makefile.beos install


This will install all files in dist-beos/, it's up to you to install the
binary and doc files to your home or to a system-wide location, so that
pecomato is found on the PATH.


		Installing from a binary archive
		================================

Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH.


		Installing from a package (.pkg, .sea)
		======================================

Open the package, and follow the installation instructions (what to install,
where to install).


	Darwin (MacOS X) installation
	=============================

Available packages for Darwin systems:

 - sources archives as .tar.gz and .tar.bz2 files (.zip and .rar can also
   be used if unzip and unrar are installed).

 - binary archives for Darwin 7.9.0 powerpc 32bit (MacOS X 10.3.19 aka Panther).


		Installing from the sources
		===========================

Pre-requisites: installing pecomato from the sources requires the GNU ANSI C
compiler to be installed (gcc), other traditional development tools are
required (GNU make 3.79, binutils). Python 1.5 mininum is required to generate
the documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers). In other word, you need to install the
Devtools.

Unpack the sources archive, enter the sources directory then:


  $ make -f Makefile.darwin
  $ make -f Makefile.darwin install


This will install all files in dist-darwin/, it's up to you to install the
binary and doc files to your user's home or to a system-wide location (as
root), preferably so that pecomato binary is found on all users' PATH.


		Installing from a binary package
		================================

Unpack the archive, enter the extracted directory and copy the pecomato binary
and doc files somewhere on the PATH, as root or not according to your
permissions or wishes.


	Microsoft Windows installation
	==============================

Running pecomato needs a common Windows system to be configured.

Available packages for win32 systems:

 - sources archive, as .zip, .rar files and self-extractible .exe (as well as
   .tar.gz and .tar.bz2 that can be used with winzip, winrar or from cygwin
   or mingw environments for instance).

 - binary archives, successfully tested on the following win32 x86 32bit OSes:
   NT4+SP6, ME, 2000, XP (vanilla, SP1 or SP2) and 2003. Other versions are
   untested yet. Those static binary archives are available as .zip, .rar and
   .exe (self-extractible) files.


		Installing from the sources
		===========================

Pre-requisites: installing pecomato from the sources requires a complete ANSI C
development system to be configured (for instance, MSVC++ 6.x and 7.x aka .NET
s OK, but the MS compiler and nmake are sufficient). The sources can be compiled
from a mingw32 or msys subsystem. Python 1.5 mininum is required to generate the
documentation. Perl 5 minimum and CVS access are necessary to build the
sources archives (for packagers). Some GNU utilies (grep, sed, etc.) are also
necessary, they are part of many distributions like UnxUtils
(http://unxutils.sf.net/), Cygwin, Mingw32/Msys, SFU.

Unpack the sources. Open a console window (cmd.exe) and enter the sources
directory then:


  $ nmake -f Makefile.win32
  $ nmake -f Makefile.win32 install


This will install all files in dist-win32/, it's up to you to install the
binary and/or doc files to your user's home or to a system-wide directory (as
an admin user, following the system), preferably so that pecomato.exe executable
is found on all users' PATH.


		Installing from a binary package
		================================

Manually unpack the archive to C:\Program files (for instance) or run the self
extracting package and select the install location.


	Installing on other OSes
	========================

You might be able to compile from the sources under some other Unices or even
different architectures, possibly with minor adaptations. Please report
successful compilations and send me the necessary changes you've made to make
is compile and run OK :-).





