[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3. Compiling and Installing the packages

Get the following individual packages:

For GNUstep Launchpad, substitute `gnustep-guile' and `jigs' for `gnustep-gui' and `gnustep-back'.

See http://www.gnustep.org for information on where to get these packages.

Make sure you install all the previously mentioned libraries first before configuring and building GNUstep (Except you need to install gnustep-objc after installing gnustep-make).

Note: you will need to be able to install packages as root (at least the base library) for applications to work correctly.

For installation on specific systems, read the machine specific instructions at the end of this document or appropriate README files in the gnustep-make Documentation directory (such as README.MingW for Windows).

3.1 Using a Display Postscript System  
3.2 Installing the Core Libraries  


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.1 Using a Display Postscript System

Please skip this instruction unless you really know what you are doing. The DPS backend is not well developed. You are better off sticking to the xlib-based backend.

Install a Display PostScript system if you want to use the XDPS backend. You do not need it if you want to use the xlib-based backend. Some systems, like Sun Microcomputers(TM) already have a DPS system installed. Linux/GNU systems need to use a free implementation of DPS (described in the Introduction.)

If you are installing DGS, follow the installation instructions included with the DGS package. If you are installing the XFree86 DPS extension, follow the instructions included with that package (and note that you need to be running XFree86 version 4.0 or greater).


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.2 Installing the Core Libraries

The GNUstep packages uses the Autoconf mechanism for configuration; it checks some host capabilties which are used by all GNUstep software. To configure just type:

 
./configure

The GNUstep makefile package needs a root directory. If the GNUSTEP_SYSTEM_ROOT environment variable is set then configure will use its value as the root directory. You can also specify the root directory when you run configure with the prefix paramter; the following command makes /usr/local/GNUstep the root directory:

 
./configure --prefix=/usr/local/GNUstep/System

If you do not have the GNUSTEP_SYSTEM_ROOT environment variable set and you do not specify a root directory when running configure, then configure will use /usr/GNUstep/System as the default root directory.

3.2.1 Alternate Library Setup  
3.2.2 Building the Package  


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.2.1 Alternate Library Setup

Read the installation instructions in the Makefile package (make) for more installation options. Make sure you use the same configuration options when configuring each GNUstep library.


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.2.2 Building the Package

To build the individual packages, use this familiar set of commands for each pacakge (add any additional options you decide upon):

 
./configure
make
make install

Start with the Makefile Pacakge (gnustep-make). After installing gnustep-make you need to execute GNUstep's shell configuration script, as follows:

 
 . /usr/GNUstep/System/Makefiles/GNUstep.sh

before proceeding any further. Then do gnustep-objc. Before building gnustep-objc, edit `GNUmakefile' and set the THREADING variable to the thread library used on your system (usually its posix, but you can leave it at single if you don't need threads). At this point you should probably re-configure, make and install gnustep-make, so it can pick up on any threading information that gnustep-objc provides.

Now do gnustep-base, gnustep-gui and finally gnustep-back.

NOTE: If you are trying to install the packages without root permission, you may need to change one thing in the base library. Edit the file gnustep-base/Tools/gdomap.h to uncomment the last line and modify the specified port number to a port which you know is not in use on your network. You should only do this if absolutely necessary since making this change will break communications with any systems where an identical change has not been made. Also, the standard gdomap port is the one officially registered with IANA and is reserved for use by gdomap - it should only be changed if you can't get your system administrator to start the gdomap server using it.


[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated by Debian/Alpha Build Daemon on April, 14 2002 using texi2html