You can always find the newest version of the software at ftp://ftp.belug.org/pub/user/mw/pilot/
Starting with V0.2.11 there is a ready to run Solaris (Sparc) binary statically linked against libpisock.a and libqt.a at ftp://ftp.belug.org/pub/user/mw/pilot/binaries/solaris/. This binary should work on any Solaris version >= 2.5.
Note: I cannot guarantee that there will always be a Solaris Sparc binary of the newest version! Usually the binaries can be found at the above mentioned location only after a short delay of several days.
From time to time users ask for precompiled binaries, so if you are willing to provide a precompiled binary for any platform this would be very appreciated. Please contact the author.
Beginning from V0.3.1 the author will provide an unofficial Debian package at:
ftp://ftp.belug.org/pub/user/mw/pilot/packages/debian/.
This package depends on the following packages:
libc6
libpisock3
libqt1g
libstdc++2.10
xlib6g
Treat this package as experimental only and please report any problems in using this package to the author only and do not submit bug reports to the Debian bug tracking system!
Beginning with V0.4.0 Matthias Kranz maintains an RPM package which will be distributed on the master ftp server at:
ftp://ftp.belug.org/pub/user/mw/pilot/packages/rpm/
This RPM package should run on SuSE and Redhat systems.
Note: I cannot guarantee that there will always be an RPM package of the newest version! Usually the RPM can be found at the above mentioned location only after a short delay of several days.
Beginning from V0.3.1 the author will provide an unofficial Solaris (Sparc) package at
Not supported anymore :(
As of V0.4.0 the build process has changed to GNU autoconf and it should be quite easy to build the program on any Unix like system.
A combination of
./configure
make
should build the binary and
make install
as root installs the binary and the documentation.
For some time the old Makefile will be distributed as Makefile.old with the package as a fallback method if the new GNU autoconf based installation process fails for some reason. Let me know if you have any problems using autoconf (please submit exact information about your system and the problem you encountered).
QT 1.3X-1.45 have been tested and are known to work. Note however that QT V2.X currently is not supported!
pilot-link.0.8.9, 0.8.11, 0.8.13, 0.9.0 and 0.9.3 have been tested and are known to work.
gcc 2.7.2 and 2.8.1 have been tested on Linux and Solaris
egcs-1.03, egcs-1.1.1 and gcc-2.9.5 have been tested on Linux and are known to work.
In general pi-address does not rely on a specific directory.
Just copy the binary to any directory which is appropriate for your system. There is a install target in the Makefile, check the variable $prefix in the Makefile, change if necessary and run make install. Depending on the directory where you want to install you may need root privileges.
The FAQ files can be accessed online by chosing Help / FAQ from the menubar.
There is an install-doc target in the Makefile, check the variable $doc_prefix in the Makefile, change if necessary and run make install-doc. This target is also run if a make install is done. Don't forget to specify this new path in your configuration file for your HelpApplication. Depending on the directory where you want to install you may need root privileges.
Specifying an empty entry for HelpApplication disables the menu Help / FAQ.
Starting with V0.1.2 there is a configuration file for the program. On startup the program searches and reads the configuration file in the following places (and in that order):
/etc/pi-addressrc
~/.pi-addressrc
The package provides an example configuration file with the program's default values. It's fairly well documented so the meanings of the key/value pairs should be obvious.