[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: handling two types of prerequisites differently in pattern rule
From: |
Philip Guenther |
Subject: |
Re: handling two types of prerequisites differently in pattern rule |
Date: |
Fri, 5 Mar 2010 11:10:11 -0800 |
On Friday, March 5, 2010, Todd Showalter <address@hidden> wrote:
...
> In this situation, I generally do:
>
> %$(ABS) : $(LD_SCRIPT) $(OBJS)
> - $(CC) $(LDFLAGS) $(TARGET_ARCH) $(filter-out %.x,$^) \
> + $(CC) $(LDFLAGS) $(TARGET_ARCH) $(OBJS) \
> $(LOADLIBES) $(LDLIBS) -o $@
>
> Rationale: if you later have additional dependencies, they'll also
> have to be filtered out, and anything that goes into that part of the
> command line for the link is going to belong in $(OBJS) anyways.
I believe that limits the solution to builds that don't use VPATH to
find the objects...which is probably Just Fine for this case, as
finding objects (as opposed to sources) with VPATH is a uncommon
setup, in my estimation.
Philip Guenther