From: Kevin Ryde <user42@zip.com.au>
Subject: Re: What to do about config.h, etc...
Date: Sat, 15 Mar 2003 09:16:45 +1000 [thread overview]
Message-ID: <878yvhv8rm.fsf@zip.com.au> (raw)
In-Reply-To: <874r67rqx6.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 13 Mar 2003 13:45:57 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
>
> After playing with the AC_CONFIG_COMMANDS approach for a while, I
> think I may have to revert to my "generate the public header via a
> small C program at build time" approach.
One approach to prefixing everything in config.h is
http://www.gnu.org/software/ac-archive/htmldoc/ac_prefix_config_h.html
Seems slightly excessive to me, since public headers probably need
relatively little of a typical config.h. But covering the whole thing
makes life easier I guess.
> AFAICT there's no way from configure.in to get
> access to the value of something that is only AC_DEFINEd.
Not unless it's also in a cache variable or something. In the case of
AC_HEADER_TIME that's $ac_cv_header_time. (Not sure if that variable
is actually documented. It follows the _cv_ convention though, so
ought to be reasonably stable.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-03-14 23:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 19:04 What to do about config.h, etc Rob Browning
2003-03-04 19:05 ` Andreas Rottmann
2003-03-04 19:53 ` Rob Browning
2003-03-05 0:55 ` Rob Browning
2003-03-13 19:45 ` Rob Browning
2003-03-14 23:16 ` Kevin Ryde [this message]
2003-03-14 23:28 ` Kevin Ryde
2003-03-05 14:18 ` Marius Vollmer
2003-03-06 22:04 ` Kevin Ryde
2003-03-07 5:25 ` Rob Browning
2003-03-11 23:18 ` Kevin Ryde
2003-03-12 3:12 ` Rob Browning
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=878yvhv8rm.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).