From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Marius Vollmer Newsgroups: gmane.lisp.guile.devel Subject: Re: pkg-config support for guile Date: 17 May 2003 01:21:00 +0200 Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Message-ID: <87wugq8omb.fsf@zagadka.ping.de> References: <87of50tdcz.fsf@raven.i.defaultvalue.org> <873cmbpyij.fsf@raven.i.defaultvalue.org> <87y937j7vq.fsf@zagadka.ping.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1053127645 1720 80.91.224.249 (16 May 2003 23:27:25 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 16 May 2003 23:27:25 +0000 (UTC) Cc: Rob Browning Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sat May 17 01:27:22 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19Gobh-0000R4-00 for ; Sat, 17 May 2003 01:27:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19Goc2-0003Bu-03 for guile-devel@m.gmane.org; Fri, 16 May 2003 19:27:42 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 19GoYG-0001IC-00 for guile-devel@gnu.org; Fri, 16 May 2003 19:23:48 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 19GoXw-0000vp-00 for guile-devel@gnu.org; Fri, 16 May 2003 19:23:29 -0400 Original-Received: from mail.dokom.net ([195.253.8.218]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19GoW2-0008IE-00 for guile-devel@gnu.org; Fri, 16 May 2003 19:21:30 -0400 Original-Received: from dialin.speedway42.dip177.dokom.de ([195.138.42.177] helo=zagadka.ping.de) by mail.dokom.net with smtp (Exim 3.36 #3) id 19GoXd-0004jG-00 for guile-devel@gnu.org; Sat, 17 May 2003 01:23:09 +0200 Original-Received: (qmail 8560 invoked by uid 1000); 16 May 2003 23:21:00 -0000 Original-To: Greg Troxel In-Reply-To: Original-Lines: 46 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 Original-cc: guile-devel@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Developers list for Guile, the GNU extensibility library List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.devel:2376 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:2376 Greg Troxel 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