[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ncurses, libtool, and os x

From: Thomas Dickey
Subject: Re: ncurses, libtool, and os x
Date: Thu, 18 Sep 2003 12:27:34 -0400 (EDT)

On Thu, 18 Sep 2003, Chris Zubrzycki wrote:

> Hash: SHA1
> On Thursday, September 18, 2003, at 12:00  PM, Thomas Dickey wrote:
> > On Thu, 18 Sep 2003, Chris Zubrzycki wrote:
> >
> >>> You could try using --with-shlib-version
> >>
> >> Well, actuaclly on os x it's named libncurses.5.0.3.dylib, but the
> >> version and compat versions are 6.x only if built with libtool. The
> >
> > so libtool makes it
> >     libncurses.6.1.4.dylib
> > or
> >     libncurses.6.0.4.dylib
> no, the file names stay exactly the same, the problem is libtool adds 1
> to whatever version is passed to it (only in darwin). I was thinking
> would it be a good idea for ncurses to decrease the version passed to
> libtool by 1 if built in darwin?

That would make it more predictable (unless of course someone got around
to fixing libtool).

> > so I see - the rules I've got for darwin use $(NCURSES_MAJOR) and
> > $(NCURSES_MINOR) rather than $(ABI_VERSION).  I think I have enough
> > information to be able to make libtool do the expected thing on my next
> > patch -- I'll add that to my to-do list.
> >
> > Note that in general it's not possible to make the versions match up,
> > since libtool uses its own convention for version numbers.
> i thought a host-specific case statement could take care of this? but
> atm the main problem i see is when the ncurses abi is increased to 6.
> then some programs will be looking for slightly different ncurses that
> have the same abi, no?

Not exactly - the script to setup libtool assumes libtool handles the
host-specific cases.

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]