unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <mwette@alumni.caltech.edu>
To: guile-user@gnu.org
Subject: Re: How to add Guile support to a package
Date: Sun, 04 Jan 2015 07:03:31 -0800	[thread overview]
Message-ID: <D51A97A3-AD4D-44CE-8D82-C9A22CD0CB2F@alumni.caltech.edu> (raw)
In-Reply-To: <CAO7R9g9uZgaoAPLjE1PGRQnwLszWprBF75vrvuLedU8VBYLkzQ@mail.gmail.com>

What you propose seems reasonable to me.   Though I have not use the AC stuff enough to say how to do it.

There is a section in the guile manual (Section 5, Section 6.4 of 2.0 manual) on embedding guile into your own program.
I believe you will need to call scm_with_guile() to get into debug mode run by guile.  You might try to run just a "hello world" example.

Does gnu chess use the boehm GC?   I wonder how that works in this case.

Matt

On Jan 4, 2015, at 5:47 AM, Antonio Ceballos <aceballos@gmail.com> wrote:

> Hi Guile folks,
> 
> I am thinking about adding guile support to GNU Chess. As it would be used as a kind of debug mode, I don't want it to have it by default, so as to avoid usually unnecessary extra dependencies. I have gone through some tutorials, and have prototyped a guile-enabled version, but it is far from working fine yet. Could you please give me some advice? I am not sure if this is the right list to post this question.
> 
> To be more specific, I would like to get something like this:
> 
> 1. Optional guile support via a configure option, being the default no guile support.
> 2. Conditional compilation of guile-enabled source code, via C precompilation directive.
> 
> More details will be necessary for sure, but I would like to have a contact with some of you guys first.
> 
> Thanks in advance!
> 
> Regards,
> Antonio Ceballos
> 




  reply	other threads:[~2015-01-04 15:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04 13:47 How to add Guile support to a package Antonio Ceballos
2015-01-04 15:03 ` Matt Wette [this message]
2015-01-05  9:59 ` John Darrington
2015-01-05 17:08 ` Ludovic Courtès
2015-01-05 17:34   ` Antonio Ceballos
2015-01-05 19:45     ` Ludovic Courtès
2015-01-06 10:26       ` Antonio Ceballos
2015-01-06 20:16     ` Hans Aberg
  -- strict thread matches above, loose matches on Subject: below --
2015-01-05  9:19 Antonio Ceballos
2015-01-05 10:05 ` Hans Aberg
2015-01-05 13:18   ` Chris Vine
2015-01-05 14:44     ` Hans Aberg
2015-01-05 16:27       ` Chris Vine
2015-01-05 17:06         ` Hans Aberg

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=D51A97A3-AD4D-44CE-8D82-C9A22CD0CB2F@alumni.caltech.edu \
    --to=mwette@alumni.caltech.edu \
    --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).