From: "Brian" <bmcandrews@eqtc.com>
Subject: RE: Guile under win32
Date: Wed, 13 Mar 2002 12:49:49 -0600 [thread overview]
Message-ID: <HIELJDHMBBPJBHNEHGIKEEMNCKAA.bmcandrews@eqtc.com> (raw)
In-Reply-To: <20020313130101.I23703@cs.virginia.edu>
> Now that I have guile going under win32, I'd like to use it with
> Microsoft's
> MFCs. I found the thread on this list from 1998 which seemed to basically
> say it wasn't doable, is this still the case?
>
> thanks again,
> --
> Chris Frost | <http://www.frostnet.net/chris/>
Not sure why it would not be doable. Maybe because, in the past, libguile
had to be initialized right at program startup, (scm_boot_guile). That's
not the case as of 1.5.??. Look at scm_init_guile. Also, read the section
on Guile Initialization Functions at http://www.lilypond.org/wiki/?Guile.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-03-13 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 20:43 Guile under win32 Chris Frost
2002-03-12 21:31 ` Chris Frost
2002-03-13 14:23 ` Brian
2002-03-13 18:01 ` Chris Frost
2002-03-13 18:49 ` Brian [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=HIELJDHMBBPJBHNEHGIKEEMNCKAA.bmcandrews@eqtc.com \
--to=bmcandrews@eqtc.com \
/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).