public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
To: Stephen Tell <tell@cs.unc.edu>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: New guile-gtk
Date: Wed, 24 May 2000 16:02:00 -0000	[thread overview]
Message-ID: <87n1lf4kjd.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.GHP.4.10.10005241700370.2159-100000@rukbat.cs.unc.edu>

Stephen Tell <tell@cs.unc.edu> writes:

> OK, I've just tried the CVS guile-gtk on SunOS 5.7 with gtk 1.2.3 and
> guile 1.3.4.

Thanks! 

> It configures and builds OK.  But when running, how can I be sure that I'm
> testing all of the new libraries and *.scm files when I've still got an
> older guile-gtk installed in /usr/local?

Hmm, you should install it in some other place and make sure
LD_LIBRARY_PATH and GUILE_LOAD_PATH point to it in the right way.  For
example, when you have installed it in /tmp/018, you would need these
settings:

    LD_LIBRARY_PATH = /tmp/018/lib
    GUILE_LOAD_PATH = /tmp/018/share/guile

However, I'm not too sure about this.  I don't know how you can check
what libraries a process is using on SunOS.  On Linux, you would look
in /proc/<pid>/maps.

> Would it be possible to add to guile-gtk.c a procedure or symbol
> guile-gtk-version that returns "0.18" (or whatever VERSION is
> defined to) ?

There will be such a thing in 0.18 (it already is in CVS). You can do

    (use-modules (gtk config))

    (if (string=? gtkconf-guile-gtk-version "0.18")
        ...)

- Marius

  reply	other threads:[~2000-05-24 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-23  6:49 Ariel Rios
2000-05-24 12:40 ` Marius Vollmer
2000-05-24 14:06   ` Stephen Tell
2000-05-24 16:02     ` Marius Vollmer [this message]
2000-05-25 10:24       ` Stephen Tell

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87n1lf4kjd.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=tell@cs.unc.edu \
    /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).