[Top][All Lists]

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

Re: Use partial relative path in LIBADD

From: Daniel Neuberger
Subject: Re: Use partial relative path in LIBADD
Date: Thu, 21 Apr 2011 10:18:14 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20101207 Thunderbird/3.1.7

On 04/20/2011 07:21 PM, Ralf Wildenhues wrote:
Why do you ever need to use the former?  (It can come in handy in
included fragments.)  The important bits are: however
you specify a file in one, you should always do it the
same way, or things may go wrong.  So a library built from the same should have a relative name; but arguably, you could
also write, e.g.,

__libfoo_la_SOURCES = ...

if you really want to make your life hard; I'd always suggest

libfoo_la_SOURCES = ...

and using plain '' in libbar_la_LIBADD.

Thanks Ralf.

I'm trying to link to a library built using a different in a different location in the source tree. I haven't been able to get the plain "" to work for that. Is there a way to do so?

The only way I've found that works is to give the complete relative path using $(top_builddir).

Sorry if I'm misunderstanding something; I really appreciate the help.

- Daniel

reply via email to

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