[Top][All Lists]

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

Re: Using nonstandard (static) lib name

From: Jan Engelhardt
Subject: Re: Using nonstandard (static) lib name
Date: Tue, 11 Nov 2008 07:34:22 +0100 (CET)
User-agent: Alpine 1.10 (LNX 962 2008-03-14)

On Monday 2008-11-10 20:53, Bob Friesenhahn wrote:
> On Mon, 10 Nov 2008, Jan Engelhardt wrote:
>> for shared libraries, it is possible to use
>>      myshared_so_LDFLAGS = -module
>> to tell automake not to warn about the missing "lib" prefix.
>> For static libraries however, something like that does not
>> work since there is no ld involved, and automake warns
>> about the missing lib prefix. Is there a flag I can use to
>> silence the warning anyway? I am only going to use the library
>> within the project itself anyway (noinst_LIBRARIES).
> Do you know for sure that the archiving tools on all the many systems your
> software might potentially run on will work as expected without the 'lib'
> prefix?

Well, I don't see why they should not be able to process
        gcc/ld -o finalprogram xyz.o myshared.a

Note that I am not even trying to use -l, but the bare filename.
        finalprogram_SOURCES = xyz.c
        finalprogram_LDADD = myshared.a

reply via email to

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