Go to the first, previous, next, last section, table of contents.
- gstep-guile
Available from
http://www.tiptree.demon.co.uk/gstep/guile/gstep-guile.tar.gz
or, for the bleeding edge - availably by anonymous cvs -
CVSROOT=":pserver:anoncvs@cvs.net-community.com:/gnustep"
export CVSROOT
cvs login (password is `anoncvs')
cvs -z3 checkout guile
- guile-1.2
Should be available from any GNU ftp site
- gstep-core-0.5.xxx
You need a snapshot from October 1998 or later - Should be available
by ftp from alpha.gnu.org or by anonymous cvs (see the 'resources' section of
http://www.gnustep.org/ for further information)
- gcc-2.8.*
Gcc should be available from any GNU ftp site
You may also use a recent version of egcs.
NB. For debugging, you need gdb-4.17 with the objc patch.
The patch for gdb-4.17 is available at
ftp://alpha.gnu.org/gnu/gnustep/contrib/
- Make sure you have gcc-2.8.* installed.
- Make sure you have Guile-1.2 or later built and installed.
This library will has been tested with both 1.2 and recent developer
snapshots of Guile.
- Make sure you have gstep-core-0.5.0 (October 1998 snapshot or later)
installed and have your account properly set up to use GNUstep.sh from
the gstep-make package to set up your environment.
- Run the `configure' script.
- To build the entire gstep-guile package, simply type 'make'
- To install - become root and type 'make install'
The installation process will copy the library into place and will also
copy Guile scripts into place.
- To test it - type 'make check'.
This will use the 'go' program (built in the Test directory) to run the
tests in 'Test/tests'.
Alternatively - you can run the 'go' program directly and work interactively.
This package has only been used by me on a GNU/Linux/Intel system -
I would love to hear about success/failures on other systems.
Likely problems - structure return is likely to fail on other systems.
it should be possible for you to fix things for your system by adding
a config file in the src/mframe directory in gstep-base and re-running
'configure' and rebuilding the base library.
Try to fix the problem. Send patches to <richard@brainstorm.co.uk>.
Go to the first, previous, next, last section, table of contents.