Next: Changes for W3Kit Versions
Up: W3Kit 2.2, An Object-Oriented Toolkit for Interactive WWW Applications

System Requirements for W3Kit Developers

Here are the libraries and tools required to build and run W3Kit applications, with links you can click to download the software:

CGI-Compliant HTTP Server:
NCSA httpd version 1.1 or higher (1.3 or higher recommended).

ANSI C and Objective-C Compiler:
GCC version 2.5.5 or higher. Versions 2.6.0-2.6.2 are not recommended (they require at least the following patch for all platforms). For SGI Irix, versions 2.6.0-2.6.3 require the following patch. NeXTSTEP developers can use the native compiler instead of GCC. Here's my script for foolproof GCC installation.

Development Libraries:
Precompiled libraries are currently available for the following platforms:

If your server platform is not listed above, you'll need to download and compile each of the following packages:

Display PostScript Libraries:
The Display PostScript Client Libraries (patched) for X11. These libraries provide a C interface to the DPS capabilities of your X server. (NeXTSTEP users don't need extra DPS libraries, but should instead obtain pbmplus for TIFF-to-GIF conversion.)
MinneGraphics Libraries:
The Geomview X11 source release, version 1.5.0 or higher. (Note that W3Kit 1.0-2.1 is compatible with OOGL 1.4.3, while W3Kit 2.2 and up is compatible with OOGL 1.5.0 an up.)
W3Kit Library:
The W3Kit class library, version 2.2 and higher.

W3Kit has been tested under Irix 4.0.x and 5.2, NeXTSTEP 3.1, SunOS 4.1.x, and Solaris 2.3.

Compiling and Installing W3Kit

The following instructions only apply if you obtained the source packages, and they assume that you have already compiled and installed everything except the W3Kit class library itself (the other packages all come with their own installation instructions).

  1. Unpack the distribution. The resulting W3Kit directory should contain at least the directories doc, include, makefiles, src, and template.

  2. Look in the makefiles directory. If a Makedefs file does not yet exist for your server platform, make a copy of Makedefs.generic and edit it to taste.

  3. Go into the src directory and edit the Makeconfig file to conform to your local system configuration. Then run make install from this directory.

  4. If you have developed any applications under W3Kit 1.0, go into the source directory for each application and run the source code upgrade script, $W3KIT/makefiles/ (where $W3KIT stands for the main W3Kit directory).

(Note: NeXTSTEP users will need to run the HTTP daemon in standalone mode from the /usr/lib/NextPrinter/lpd.children script, in order to give W3Kit access to the window server.)

Next: Changes for W3Kit Versions
Up: W3Kit 2.2, An Object-Oriented Toolkit for Interactive WWW Applications

[HOME] The Geometry Center Home Page

Author: Paul Burchard
Comments to:
Created: Apr 18 1994 --- Last modified: Tue Jun 18 10:20:53 1996