unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-devel@gnu.org
Subject: Re: What to do about config.h, etc...
Date: Tue, 04 Mar 2003 20:05:19 +0100	[thread overview]
Message-ID: <87bs0r3qc0.fsf@alice.rotty.yi.org> (raw)
In-Reply-To: <87vfyzoswd.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Tue, 04 Mar 2003 13:04:18 -0600")

Rob Browning <rlb@defaultvalue.org> writes:

> In 1.6 and 1.7, configure has been changed to generate config.h rather
> than libguile/scmconfig.h, and now libguile/scmconfig.h is generated
> from ../config.h using sed.  During this process sed removes
> autoheader's global PACKAGE #define, so that it won't conflict with
> any other package's public headers.
>
[snip]

> To make things more difficult, AFAICT the auto* tools don't really
> provide us with any easy mechanism to fix this problem.  Off the top
> of my head I can see three choices:
>
>   - Edit configure.in to change all symbols produced by configure to
>     have SCM_ prefixes and just keep #including a copy of the
>     automatically generated header (i.e. no private symbols) as we do
>     now.  [...]
>   - Use sed or similar to mangle config.h into a public and private
>     header (or perhaps to just rename FOO -> SCM_FOO globally).  [...]
>
>   - Use a C program to translate from config.h to the public and
>     private headers, i.e. write a trivial C program that is built at
>     compile time, that #includes config.h, [...]

If you take a look at how other libraries, (e.g. GLib) do this, you'll
see that most of them that need a public-installed, platform-specific
header, use autoconf's AC_CONFIG_COMMANDS macro to generate that
header by a shell script run at configure time.

Regards, Andy
-- 
Andreas Rottmann         | Dru@ICQ        | 118634484@ICQ | a.rottmann@gmx.at
http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-03-04 19:05 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 [this message]
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
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=87bs0r3qc0.fsf@alice.rotty.yi.org \
    --to=a.rottmann@gmx.at \
    --cc=guile-devel@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).