[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: prog_DEPENDENCIES
From: |
Bob Rossi |
Subject: |
Re: prog_DEPENDENCIES |
Date: |
Wed, 14 Feb 2007 10:19:20 -0500 |
User-agent: |
Mutt/1.5.12-2006-07-14 |
On Mon, Jan 29, 2007 at 07:52:02PM +0100, Ralf Wildenhues wrote:
> > BTW, all the _DEPENDENCIES that I'm talking about are
> > libraries that are built from my own project, but not necessarily in the
> > same Makefile.
>
> OK. You will have to make sure these libraries exist and are up to
> date, when they are needed. Typically by recursing to that other
> Makefile earlier (i.e., by way of SUBDIRS ordering).
>
> For libraries built from the same Makefile, please note that typically,
> make implementations are not smart enough to discover that
> $(top_builddir)/sub/libfoo.la (with top_builddir = ..)
> ./libfoo.la
> libfoo.la
>
> all refer to the same file, even if they are the same file. So if you
> have a rule for the latter, but depend upon one of the former two,
> things can break. GNU make identifies the latter two.
Hi,
One other question. This is in regards to libraries depending on
libraries. If library B depends on library A, do I have to put a
libB_a_DEPENDENCIES = $(top_builddir)/..../libA.a
or does just having the SUBDIRS traverse in the correct order work?
Thanks,
Bob Rossi
- Re: prog_DEPENDENCIES,
Bob Rossi <=