unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: Rob Browning <rlb@defaultvalue.org>
Subject: Re: pkg-config support for guile
Date: 17 May 2003 01:21:00 +0200	[thread overview]
Message-ID: <87wugq8omb.fsf@zagadka.ping.de> (raw)
In-Reply-To: <rmik7dkj4dw.fsf@fnord.ir.bbn.com>

Greg Troxel <gdt@ir.bbn.com> writes:

>   [I sent a patch to add pkg-config support.]
> 
>   I don't think we should offer two ways to get configuration
>   information about Guile.  When pkgconfig is better than our current
>   method, we should use it exclusively.  When not, we should keep our
>   current stuff.
> 
> pkgconfig is better in that programs that use guile will not have to
> include a guile-specific m4 fragment into configure - there is a
> standard pkgconfig m4 fragment that suffices to link all programs that
> use pkgconfig for config info.
>
> But programs needing GUILE_MODULE_FOO will still need the guile m4.
> This is really a separate problem from guile-config - using guile as a
> scripting language rather than a libary, so not trying to use
> pkgconfig here seems fine.
> 
> I don't understand why you think there should not be two ways.  Users
> can use whichever way they like better, and this makes guile more
> friendly.

Yes, I agree.  I wasn't precise enough when I said "there should not
be two ways to get confiuration information about Guile".  I was
really only thinking about how we maintain the code for exporting this
configuration information, not about how users will access it.  That
is, my only worry is that when add support for pkg-config, and
continue to offer guile-config (which we should), then there is the
risk that the two mechanism diverge over time when they are separately
implemented.  There should only be a single point in the code where
the exported configuration information is defined and both user
interfaces (pkg-config and guile-config) should draw from that source.

For example, the "Libs:" line in guile.pc needs to stay in sync with
the corresponding stuff in guile-config.  This should happen
automatically.

Also, we will need documentation for how to use pkg-config with Guile,
maybe with a pointer to generic pkg-config.

That's what keeps me from applying the patch right away (and I hope
others agree that it is not unreasonable).

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


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


  reply	other threads:[~2003-05-16 23:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 12:37 Release now? Mikael Djurfeldt
2003-02-24 13:08 ` Dale P. Smith
2003-02-24 13:21   ` Mikael Djurfeldt
2003-02-24 13:32 ` Greg Troxel
2003-02-25 13:34   ` Marius Vollmer
2003-02-25 16:08     ` Greg Troxel
2003-02-25 18:38       ` Rob Browning
2003-02-26  1:51         ` Greg Troxel
2003-02-26  2:27           ` Rob Browning
2003-02-27 14:25             ` Greg Troxel
2003-02-27 15:21               ` pkg-config support for guile Greg Troxel
2003-03-22 23:31                 ` Marius Vollmer
2003-04-23 21:22                   ` Greg Troxel
2003-05-16 23:21                     ` Marius Vollmer [this message]
2003-02-27 16:54               ` Release now? Rob Browning
2003-02-27 18:07                 ` Greg Troxel
2003-02-27 18:45                   ` Rob Browning
2003-02-27 19:25                     ` Greg Troxel
2003-02-27 20:14                       ` Rob Browning
2003-02-27 19:06                 ` Rob Browning
2003-02-27 19:13                   ` Rob Browning
2003-02-27 19:36                     ` Greg Troxel
2003-02-27 20:02                       ` Rob Browning
2003-02-27 20:54                         ` Greg Troxel
2003-02-27 21:07                           ` Dale P. Smith
2003-02-27 21:30                             ` Dale P. Smith
2003-02-27 21:47                           ` Rob Browning
2003-04-25 19:26                           ` Neil Jerram
2003-02-25 16:28     ` Andreas Rottmann
2003-02-24 18:35 ` Rob Browning
2003-02-25 13:20 ` Marius Vollmer
2003-03-03 14:06   ` Mikael Djurfeldt
2003-04-25 19:28   ` Neil Jerram
2003-04-25 22:59     ` 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=87wugq8omb.fsf@zagadka.ping.de \
    --to=mvo@zagadka.de \
    --cc=rlb@defaultvalue.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).