mirror/guile
mirror/guile
1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-06-09 21:40:33 +02:00
Code Activity

*** empty log message ***

Browse source
This commit is contained in:
Jim Blandy 1999-09-17 16:40:50 +00:00
parent 09cbffcde1
commit 18f468f8ca
1 changed files with 8 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

24
INSTALL
View file

@ -73,10 +73,10 @@ libqt.a, which you will need to link into your programs after
libguile.a. That is, you should pass the switches -lguile -qt to your libguile.a. That is, you should pass the switches -lguile -qt to your
linker. linker.
Coop threads are not yet thoroughly tested; once they are, they will Cooperative threads are not yet thoroughly tested; once they are, they
be enabled by default. The interaction with blocking I/O is pretty ad will be enabled by default. The interaction with blocking I/O is
hoc at the moment. In our experience, bugs in the thread support do pretty ad hoc at the moment. In our experience, bugs in the thread
not affect you if you don't actually use threads. support do not affect you if you don't actually use threads.
--enable-dynamic-linking --- Build a Guile executable and library --enable-dynamic-linking --- Build a Guile executable and library
providing Scheme functions which can load a shared library and providing Scheme functions which can load a shared library and
@ -102,24 +102,16 @@ separate build directory, you'll need to include the build directory
in the path as well. in the path as well.
For example, suppose the Guile distribution unpacked into a directory For example, suppose the Guile distribution unpacked into a directory
called `/home/jimb/guile-snap' (so the full name of this file would be called `/home/jimb/guile-snap' (so the full name of this INSTALL file
`/home/jimb/guile-snap/INSTALL'). Then you might say: would be `/home/jimb/guile-snap/INSTALL'). Then you might say, if
you're using Bash or any other Bourne shell variant,
export GUILE_LOAD_PATH=/home/jimb/guile-snap export GUILE_LOAD_PATH=/home/jimb/guile-snap
if you're using Bash or any other Bourne shell variant, or or if you're using CSH or one of its variants:
setenv GUILE_LOAD_PATH /home/jimb/guile-snap setenv GUILE_LOAD_PATH /home/jimb/guile-snap
if you're using CSH or one of its variants.
If you built Guile in a separate directory from the source tree, then
you'll need to include your build directory in the GUILE_LOAD_PATH as
well. For example, if you built in a subdirectory of the source tree
called `pentium', you might say:
export GUILE_LOAD_PATH=/home/jimb/guile-snap:/home/jimb/guile-snap/pentium
Building a Statically Linked Guile ======================================== Building a Statically Linked Guile ========================================