From: Mike Gran <spk121@yahoo.com>
To: Panicz Maciej Godek <godek.maciek@gmail.com>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: A [serious] problem with module integration
Date: Fri, 16 Nov 2012 08:03:59 -0800 (PST) [thread overview]
Message-ID: <1353081839.32769.YahooMailNeo@web120405.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CAMFYt2YdPm2g47+OgXxDXDqOzgCPYrPjpWjJUt8rFmN5EOsaBw@mail.gmail.com>
Hello Panicz-
> From: Panicz Maciej Godek <godek.maciek@gmail.com>
> And now I have a problem: the modules that I wrote make use
> of the symbols defined by my application (using scm_c_define...),
> but they are unavailable outside my application, i.e. for external
> modules.
[snip]
I read this, and I am having a bit of trouble visualizing
what you've done, but, perhaps your problem can be fixed
by simply replacing scm_c_define with scm_c_export.
So try that first.
In any case, I pretty sure I did what you are trying to
when I added guile handling to a private build of the Zile
editor. Re http://github.com/spk121/zile . This is a bit
more elaborate because I wanted my exported functions
to be in their own named module
If I recall correctly, (cause I haven't touched this code
in a while), in my C code that defines the Guile exports,
I did this.
- created a new module called 'zile' to hold my functions using
scm_c_resolve_module("zile")
- defined my functions into that module with
scm_c_export
- switched back to the (guile user) environment
with scm_c_resolve_module("guile-user")
- loaded my newly defined module using
scm_c_use_module("zile")
Hope this correct, and that it helps.
-Mike Gran
next prev parent reply other threads:[~2012-11-16 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 13:54 A [serious] problem with module integration Panicz Maciej Godek
2012-11-16 16:03 ` Mike Gran [this message]
2012-11-16 16:10 ` Mike Gran
2012-11-16 16:38 ` Panicz Maciej Godek
2012-11-16 16:41 ` Mark H Weaver
2012-11-16 17:10 ` Mike Gran
2012-11-16 20:40 ` Ludovic Courtès
2012-11-17 20:28 ` rixed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1353081839.32769.YahooMailNeo@web120405.mail.ne1.yahoo.com \
--to=spk121@yahoo.com \
--cc=godek.maciek@gmail.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).