> -----Original Message----- > From: Vincent Torri [mailto:vincent.to...@gmail.com] > Sent: Thursday, March 05, 2015 1:26 PM > To: Andy Falanga (afalanga) > Cc: Thomas Jahns; automake@gnu.org > Subject: Re: How to use ld options correctly for --whole-archive in > automake and libtool > > On Thu, Mar 5, 2015 at 8:04 PM, Andy Falanga (afalanga) > <afala...@micron.com> wrote: > >> -----Original Message----- > >> From: Vincent Torri [mailto:vincent.to...@gmail.com] > >> Sent: Thursday, March 05, 2015 10:44 AM > >> To: Andy Falanga (afalanga) > >> Cc: Thomas Jahns; automake@gnu.org > >> 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
I see, thanks.
