From: Peter Brett <peter@peter-b.co.uk>
To: guile-user@gnu.org
Subject: Re: Checking for guile from configure -- forward compat.
Date: Fri, 14 Aug 2009 08:26:41 +0100 [thread overview]
Message-ID: <we1mhbwadff2.fsf@ssclt003.ee.surrey.ac.uk> (raw)
In-Reply-To: m3my6adcsp.fsf@harrington.peter-b.co.uk
Peter TB Brett <peter@peter-b.co.uk> writes:
> Hi everyone,
>
> Currently, there appear to be two ways to check for the presence of
> Guile:
>
> PKG_CHECK_MODULES(GUILE, [guile-1.8])
>
> Or:
>
> GUILE_FLAGS
>
> Unfortunately, the first of these *only* works for Guile 1.8 -- so if
> some has, at some point in the future, Guile 2.x, we'll have to add
> some m4 magic for sequentially trying 1.8 and every valid x for 2.x.
>
> On the other hand, GUILE_FLAGS uses the guile-config tool, which IIRC is
> going to go away Soon (tm).
>
> What would you recommend as the Right Way to check for Guile 1.8.0 or
> later in my configure script and set the appropriate flags, in a
> forward-compatible way? Or am I just going to have to write a pile of
> crufty m4/shell?
We ended up writing a pile of crufty m4/shell, which:
- checks for guile-1.8.pc
- if that fails, checks for guile-2.0.pc
- if that fails, checks for guile-config
http://git.gpleda.org/?p=gaf.git;a=blob;f=m4/geda-guile.m4;hb=HEAD
Ewww.
Peter
--
Peter Brett <peter@peter-b.co.uk>
Remote Sensing Research Group
Surrey Space Centre
next prev parent reply other threads:[~2009-08-14 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 6:45 Checking for guile from configure -- forward compat Peter TB Brett
2009-08-08 16:59 ` Linas Vepstas
2009-08-08 19:39 ` Peter TB Brett
2009-08-13 22:12 ` Neil Jerram
2009-08-14 1:36 ` Andreas Rottmann
2009-08-14 21:31 ` Neil Jerram
2009-08-14 7:26 ` Peter Brett [this message]
2009-08-14 21:32 ` Neil Jerram
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=we1mhbwadff2.fsf@ssclt003.ee.surrey.ac.uk \
--to=peter@peter-b.co.uk \
--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).