unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: rixed@happyleptic.org
To: guile-user@gnu.org
Subject: Re: A [serious] problem with module integration
Date: Sat, 17 Nov 2012 21:28:47 +0100	[thread overview]
Message-ID: <20121117202847.GA3605@ombreroze.happyleptic.org> (raw)
In-Reply-To: <CAMFYt2YdPm2g47+OgXxDXDqOzgCPYrPjpWjJUt8rFmN5EOsaBw@mail.gmail.com>

-[ Fri, Nov 16, 2012 at 02:54:50PM +0100, Panicz Maciej Godek ]----
> 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.
> 
> The result is that the modules don't work, because certain symbols
> are undefined that are needed to build the necessary definitions.

I have run into a similar problem recently: I'm defining from C the
module 'runtime' where I store all my scm_d_defined symbols and when
compiling a guile module (using "guile-tool compile") the compiler
looks for a file named runtime.scm and of course fails to find one
and stops.

To solve this I had to create a void runtime.scm file defining this
dummy module so that other modules can be compiled. You can see the
result here:

http://github.com/securactive/junkie/blob/master/guile/junkie/runtime.scm

There might be better solutions to this problem but this one is
particularly easy to implement.




      parent reply	other threads:[~2012-11-17 20:28 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
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 [this message]

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=20121117202847.GA3605@ombreroze.happyleptic.org \
    --to=rixed@happyleptic.org \
    --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).