[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to use ld options correctly for --whole-archive in automake and
From: |
Vincent Torri |
Subject: |
Re: How to use ld options correctly for --whole-archive in automake and libtool |
Date: |
Thu, 5 Mar 2015 21:26:10 +0100 |
On Thu, Mar 5, 2015 at 8:04 PM, Andy Falanga (afalanga)
<address@hidden> wrote:
>> -----Original Message-----
>> From: Vincent Torri [mailto:address@hidden
>> Sent: Thursday, March 05, 2015 10:44 AM
>> To: Andy Falanga (afalanga)
>> Cc: Thomas Jahns; address@hidden
>> Subject: Re: How to use ld options correctly for --whole-archive in
>> automake and libtool
>>
>> >
>> >> But what exactly is the problem with using e.g. ../Shared/HwMgmt/
>> >> libhwmgmt.la? That sata.so will then require libhwmgmt.so? libtool
>> >> should be able to set sata.so's rpath such that libhwmgmt.so will be
>> >> found at runtime.
>>
>> I would also use $(top_builddir) instead of relative path. It could
>> help when building in another directory than the source one (like with
>> make distcheck)
>>
>
> Vincent,
>
> I am an automake/autotools neophyte. I have to plead ignorance at the use
> of $(top_builddir). I've read some of what this variable is supposed to be
> but I'm not sure. What is its value? How is used in the scripts?
something like :
my_lib_LDADD = $(top_builddir)/Shared/HwMgmt/libhwmgmt.la
Vincent Torri
Re: How to use ld options correctly for --whole-archive in automake and libtool, Gavin Smith, 2015/03/05