From: ludovic.courtes@laas.fr (Ludovic Courtès)
To: "Marco Maggi" <marco.maggi-ipsu@poste.it>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: guile pkg-config meta file?
Date: Mon, 08 Oct 2007 09:55:19 +0200 [thread overview]
Message-ID: <874ph2kplk.fsf@laas.fr> (raw)
In-Reply-To: <JPGH2V$469351D65A6897CBD016F15503415829@poste.it> (Marco Maggi's message of "Fri\, 5 Oct 2007 22\:32\:55 +0200")
Hi,
"Marco Maggi" <marco.maggi-ipsu@poste.it> writes:
> is there a specific reason for Guile not to install a
> pkg-config meta file?
No. It's a good idea and it helps in some cases (e.g.,
cross-compilation). Many people already suggested this and I think it
will appear "sooner or later" in HEAD. :-)
Thanks,
Ludovic.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2007-10-08 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 20:32 guile pkg-config meta file? Marco Maggi
2007-10-08 7:55 ` Ludovic Courtès [this message]
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=874ph2kplk.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-user@gnu.org \
--cc=marco.maggi-ipsu@poste.it \
/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).