[Top][All Lists]

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

Re: Using libtool for linking

From: Jason Curl
Subject: Re: Using libtool for linking
Date: Fri, 17 Aug 2007 20:42:28 +0200
User-agent: Thunderbird (Windows/20070728)

Peter O'Gorman wrote:
On Fri, 2007-08-17 at 13:29 +0200, Jason Curl wrote:
As for testing the situation, AC_CHECK_LIB makes me believe it will work. But it only works in a subset of cases (i.e. static only). I have another implementation that I can compile in but at the moment there is no indication I should use my own internal implementation (I'd rather use an external implementation where possible in the belief it's probably been better debugged).

So, ideas how to work around this problem to achieve my goal?
Why not import the libiberty sources into your project and build a
convenience libiberty.
I'd rather use what's already installed.
AC_CHECK_LIB does not check for static/shared/can be used as input by
libtool, nor should it, imo.
What if I come across something else that's not libiberty that has no shared library? or more likely no .la files? The autotools documentation goes to a bit of length to show how it's done without libtool.

So, is there something to check if it will work shared or static or both (if it's not going to be AC_CHECK_LIB)? Then at least the user can be warned. Seeing as libtool does a lot of this in anycase, maybe something just needs to be exposed?

reply via email to

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