[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Converting a project to libtool
From: |
Jeff Bailey |
Subject: |
Re: Converting a project to libtool |
Date: |
Wed, 18 Sep 2002 21:25:41 -0700 |
User-agent: |
Mutt/1.3.28i |
On Wed, 18 Sep 2002 19:32:00 -0400, Steve M. Robbins wrote:
>> I'm converting a project to libtool, and need to maintain the
>> existing SONAME and library names. I can't find a FAQ to see if
>> there's a good way to do this.
>I think the answer is "no, there's no good way to do this".
>This is mainly because when you pass "-version-info C:R:A" to
>libtool, the SONAME that results can be different between different
>systems. Indeed, some systems (IRIX, I think) don't even have a
>single SONAME.
>If you aim a bit lower, and are only concerned about keeping the
>SONAME for one system, say linux, then you can just reverse-engineer
>the computation that libtool does. Then choose values for Current,
>Revision, and Age that give you the answer you want.
I did that, and 0:0:3 gives me an "age is greater than current
interface" error.
Would perhaps a "--disable-sanity-checks" flag be permissable for this
then? My biggest problem is that in doing this whole converting to
auto*/libtool, I have no good way of testing to make sure that I've
got it all right because that would involve recompiling everything.
There's a few places where there's room for subtle ABI weirdness and
I'd like to be able to know for certain that I haven't done anything
wrong. Certainly after this, this right thing is to switch to
-version-info
--
learning from failures is nice in theory...
but in practice, it sucks :)
- Wolfgang Jaehrling