-
Notifications
You must be signed in to change notification settings - Fork 1
/
README
69 lines (49 loc) · 2.35 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
Overview
--------
This library provides a thread safe event loop for guile-2.0
(event-loop.scm) with support for watches on ports/file descriptors
and timeouts, and which permits events to be posted by other tasks.
This includes tasks running on other threads.
It also provides a coroutines interface (coroutines.scm) which
provides await semantics on such events, so as to avoid inversion of
control (aka "callback hell").
See the documentation mentioned below for further details, and the
docs/example.scm and docs/example-glib.scm files.
A separate guile-a-sync2 library is available for guile-2.2 and
guile-3.0 here: https://github.com/ChrisVine/guile-a-sync2 , and a
guile-a-sync3 library is available for guile-3.0 only here:
https://github.com/ChrisVine/guile-a-sync3 . This library is parallel
installable with guile-a-sync2 or with guile-a-sync3. Where a program
is to be heavily i/o based, say it is based on sockets, and
guile-2.2/3.0 is available, guile-a-sync2 or guile-a-sync3 is
recommended as they make use of guile's suspendable ports.
Installation
------------
When first run from git, or a tarball obtained from github, it is
necessary to set up autotools. This can be done with:
./autogen.sh --prefix=/usr
or on a 64-bit system, probably:
./autogen.sh --prefix=/usr --libdir=/usr/lib64
This generates a configure script and installs libtool. Subsequent
configuration can be done just with
./configure --prefix=/usr
and
./configure --prefix=/usr --libdir=/usr/lib64
respectively.
On a 64 bit system you may also need to include -fPIC in your CFLAGS
options if libtool doesn't do that for you (libtool normally does when
necessary).
After compiling, install with 'make install' as root.
By default, the scheme files provided by this library will be
pre-compiled to guile bytecode and installed with the scheme files in
guile's object file directory. If that behaviour is not wanted (say,
because a unix-like compile environment is not available which is
acceptable to the compile scripts), then configure with the
--disable-compile-to-bytecode option.
Documentation
-------------
Html documentation is available after installation in the default html
directory for the target installation (normally at
$(prefix)/share/doc/guile-a-sync/html/index.html).
In addition, the documentation can be viewed at github at:
https://github.com/ChrisVine/guile-a-sync/wiki