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

3. Compiling and Installing the packages

Get the following individual packages:

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

Make sure you install (if necessary) all the previously mentioned libraries first before configuring and building GNUstep.

You should install these packages as root (read special note for the gnustep-base library, below, if you cannot do this).

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).

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

3.1 Installing the Core Libraries

The GNUstep packages uses the Autoconf mechanism for configuration; it checks some host capabilities which are used by all GNUstep software. The first package you will compile is gnustep-make. To configure gnustep-make just type:


The GNUstep makefile package can be configured to use different types of filesystem layouts. By default, GNUstep is installed with a Unix-style filesystem layout into /usr/local/. That is a good, recommended default if you don’t have an opinion on which filesystem layout to use.

But you can also install it somewhere else by using the prefix parameter; the following command installs it in /opt/GNUstep:

./configure --prefix=/opt/GNUstep

You can also install GNUstep using a GNUstep layout (or some other filesystem layout of your choice) by using the with-layout parameter; the following command configures GNUstep to use the traditional GNUstep layout:

./configure --with-layout=gnustep

In this document we will always present examples that assume that you are using the default filesystem layout in /usr/local/. If you are using a different layout, you will need to make the obvious changes.

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

3.1.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.1.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):

make install

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

 . /usr/local/share/GNUstep/Makefiles/GNUstep.sh

before proceeding any further.

NOTE for gcc 2.X or MinGW users: Now install gnustep-objc. Before building gnustep-objc, edit the ‘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 install 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 Adam Fedor on December 24, 2013 using texi2html 1.82.