From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Neil Jerram Newsgroups: gmane.lisp.guile.devel Subject: Purpose of guile-xxx executables? Date: 12 Sep 2002 22:12:16 +0100 Sender: guile-devel-admin@gnu.org Message-ID: NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1031866144 20091 127.0.0.1 (12 Sep 2002 21:29:04 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 12 Sep 2002 21:29:04 +0000 (UTC) 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 17pbWI-0005Ds-00 for ; Thu, 12 Sep 2002 23:29:02 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17pbWO-0006GU-00; Thu, 12 Sep 2002 17:29:08 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 17pbWB-0006G0-00 for guile-devel@gnu.org; Thu, 12 Sep 2002 17:28:55 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 17pbW7-0006Fm-00 for guile-devel@gnu.org; Thu, 12 Sep 2002 17:28:54 -0400 Original-Received: from mail.uklinux.net ([80.84.72.21] helo=s1.uklinux.net) by monty-python.gnu.org with esmtp (Exim 4.10) id 17pbW7-0006Fi-00 for guile-devel@gnu.org; Thu, 12 Sep 2002 17:28:51 -0400 Original-Received: from portalet.ossau.uklinux.net (ppp-1-10.lond-b-4.access.uk.tiscali.com [80.40.19.10]) by s1.uklinux.net (8.11.6/8.11.6) with ESMTP id g8CLSnm27990 for ; Thu, 12 Sep 2002 22:28:49 +0100 Original-Received: from laruns.ossau.uklinux.net.ossau.uklinux.net (laruns.ossau.uklinux.net [192.168.1.3]) by portalet.ossau.uklinux.net (Postfix on SuSE Linux 7.2 (i386)) with ESMTP id E7BAB1702 for ; Thu, 12 Sep 2002 22:18:05 +0000 (GMT) Original-To: Guile Development Original-Lines: 24 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:1331 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:1331 In the last release of my guile-xlib package, I included a guile-xlib executable that was identical to vanilla Guile except that it was linked with my library and called scm_register_module_xxx(...) just before scm_shell. For the next release, I've changed to using dynamic-link and dynamic-call, so the scm_register_module_xxx goes away. Given this, is there any point anymore in building the guile-xlib executable? Two possibilities occur: - building an executable allows me to check that my library doesn't contain any unresolved externals - something to do with platforms that only perform static linking. However, it seems to me that, on both these points, we should instead have some more generic tool that allows the building of a custom Guile with, in general, several libraries statically prelinked in, e.g. Guile + libguilexlib + libguilegtk + libguilepg. Is this correct? If so, how should it work in detail? Neil _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel