From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: Testing for a GUILE installation
Date: Thu, 10 Oct 2002 11:18:51 -0700 [thread overview]
Message-ID: <E17zhtb-0001ZR-00@giblet> (raw)
In-Reply-To: <20021010130232.GK8806@nemesis.xlii.org> (message from David Allouche on Thu, 10 Oct 2002 15:02:32 +0200)
From: David Allouche <david@allouche.net>
Date: Thu, 10 Oct 2002 15:02:32 +0200
recommended, less hackish, way of
testing that GUILE is correctly installed.
use GUILE_PROGS macro in configure.in. call aclocal in your autogen.sh
script (or equivalent). this adds a check for guile and guile-config to
be run at configure-time. see guile.m4 for other checks:
## GUILE_PROGS -- set paths to Guile interpreter, config and tool programs
## GUILE_FLAGS -- set flags for compiling and linking with Guile
## GUILE_SITE_DIR -- find path to Guile "site" directory
## GUILE_CHECK -- evaluate Guile Scheme code and capture the return value
## GUILE_MODULE_CHECK -- check feature of a Guile Scheme module
## GUILE_MODULE_AVAILABLE -- check availability of a Guile Scheme module
## GUILE_MODULE_REQUIRED -- fail if a Guile Scheme module is unavailable
## GUILE_MODULE_EXPORTS -- check if a module exports a variable
## GUILE_MODULE_REQUIRED_EXPORT -- fail if a module doesn't export a variable
for automated generation of some of these macro "calls", create
top-level file modules.af w/ contents:
(files-glob "scheme/*.scm" "etc/*.scm") ; munge paths to taste
add in autogen.sh:
guile-tools autofrisk
and modify the aclocal call to include cwd:
aclocal -I .
this adds checks for those modules referenced in scheme/*.scm and
etc/*.scm to be run at configure-time. look at autofrisk commentary for
ways to fine-tune these checks. here are some examples:
http://www.glug.org/people/ttn/software/etrack/dist/0.86/modules.af
http://www.glug.org/people/ttn/software/ttn-pers-scheme/dist/0.31/modules.af
see also autogen.sh files in the same directories.
lastly, in general you should not check for program version number as an
indirect indicator of some feature; check for the feature specifically.
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-10-10 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 12:32 [bug] guile-config info top_srcdir David Allouche
2002-10-10 13:02 ` Testing for a GUILE installation David Allouche
2002-10-10 18:18 ` Thien-Thi Nguyen [this message]
2002-10-11 21:37 ` Neil Jerram
2002-10-14 22:34 ` Marius Vollmer
2002-10-15 8:17 ` David Allouche
2002-10-18 21:58 ` Marius Vollmer
2002-10-14 22:27 ` [bug] guile-config info top_srcdir Marius Vollmer
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=E17zhtb-0001ZR-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).