33 |
|
|
34 |
With respect to (2) |
With respect to (2) |
35 |
|
|
36 |
|
Current assumptions (though likely open to debate): |
37 |
|
|
38 |
|
(1) Guile shared libs, even ones supporting modules may need to be |
39 |
|
directly linked into applications via -l. For example, if you |
40 |
|
want to call scm_make_u8vector from srfi-4 in your scheme code, |
41 |
|
you will need to be able to "-l link" against |
42 |
|
libguile-srfi-srfi-4 (or whatever lib contains that function). |
43 |
|
This requirement places certain restrictions on the possible |
44 |
|
solutions we might design. |
45 |
|
|
46 |
A proposal: |
A proposal: |
47 |
|
|
48 |
(1) Write our own lt_dlopen(char *name, unsigned int interface) |
(1) Write our own lt_dlopen(char *name, unsigned int interface) |