Hi,
I've been making some tiny changes in the way my application
uses modules. Previously I was including the scheme code right
into the C binary. This wasn't particularly elegant sollution, as it
didn't allow the code to be compiled, so I decided that I use guile
modules wherever I can.
And now I
Hello Panicz-
> From: 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.
[snip]
I read this, and I am having a bit o
> From: Mike Gran
> To: Panicz Maciej Godek ; "guile-user@gnu.org"
>
> Cc:
> Sent: Friday, November 16, 2012 8:03 AM
> Subject: Re: A [serious] problem with module integration
>
> Hello Panicz-
>
>> From: Panicz Maciej Godek
>> And now I have a problem: the modules that I wrote make use
>> o
2012/11/16 Mike Gran :
> 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.
Oh yes, it helped. Thanks a lot!
Mike Gran writes:
>> From: 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.
>
> If I recall correctly, (cause I
> From: Mark H Weaver
> Mike Gran writes:
>
> What Mike wrote here is almost correct, but there were a few mistakes.
Thanks for clarifying.
-Mike Gran
Hi!
Panicz Maciej Godek skribis:
> If I'd taken a different approach, e.g. if I'd decided to use shared
> libraries instead of having the main application call scm_with_guile,
> the solution would be easy -- I could just define the wrappers around
> the procedures exported by the library.
Yes.
