public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Steve Tell <tell@telltronics.org>
To: Ariel Rios <jarios@usa.net>
Cc: Guile-GTK List <guile-gtk@sourceware.cygnus.com>
Subject: Re: Guile-gtk 0.19pre
Date: Mon, 10 Jul 2000 20:50:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0007102333000.31256-100000@ariel.lan.telltronics.org> (raw)
In-Reply-To: <20000706043906.28221.qmail@nwcst319.netaddress.usa.net>

	Thanks for assembling this; it seems to build nicely, (but only
tried on a vanilla Redhat6.2/Intel so far).

The 0.19 prerelease still builds its shared libraries with names like
"libguilegtk-1.2.so.0.0.0"

Should the numbers be incremented to help indicate that this .so isn't 
compatible with the old one?   Or is it actually drop-in-replacable?

Guile itself appears to have these library versions:
	guile-1.3.4	libguile.so.6.0.0
	guile-1.4	libguile.so.9.0.0

Everything I know about libtool versioning comes from:

http://www.gnu.org/software/libtool/manual.html#Libtool%20versioning

It looks as simple as passing the appropriate arg to the -version-info
libtool option;  I think 0:1:0 might be the appropriate one given that the
only changes are internal ones to build with guile 1.4.

Steve


On 5 Jul 2000, Ariel Rios wrote:

> I have uploaded the first 0.19 prerelease. This version supports
> new guile 1.4. Besides this 1.4 support there is nothing new in it.
> 
> Check it at:
> http://www.netpedia.net/hosting/erin/download/guile-gtk-01.9pre.tar.gz
> 
> ariel
> 
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
> 

  parent reply	other threads:[~2000-07-10 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-05 21:38 Ariel Rios
2000-07-06  7:46 ` Greg J. Badros
2000-07-10 20:50 ` Steve Tell [this message]
2000-07-17 12:14   ` 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

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

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0007102333000.31256-100000@ariel.lan.telltronics.org \
    --to=tell@telltronics.org \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=jarios@usa.net \
    /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).