%% Sam Ravnborg <[EMAIL PROTECTED]> writes:
sr> On Fri, Oct 03, 2003 at 05:26:54PM -0400, Paul D. Smith wrote:
>> No make expands $* in the prerequisites list to the name of the target.
sr> Hmmm..
sr> foo.o : _$* FORCE
sr> echo $^
sr> FORCE:
sr> I expected make to print out:
On Fri, Oct 03, 2003 at 05:18:04PM -0400, Paul D. Smith wrote:
>
> sr> Is it coorect behaviour that make does not expand the variable
> sr> $(deps_foo.o)?
>
> Yes, because that's not the variable you asked to expand. You asked it
> to expand the variable $(deps_%).
Got it now, found the rig
On Fri, Oct 03, 2003 at 05:26:54PM -0400, Paul D. Smith wrote:
>
> No make expands $* in the prerequisites list to the name of the target.
Hmmm..
foo.o : _$* FORCE
echo $^
FORCE:
I expected make to print out:
make: *** No rule to make target `_foo.o', needed by `foo.o'. Stop.
But I g
%% Sam Ravnborg <[EMAIL PROTECTED]> writes:
sr> Is there any other way to get the name of the target
sr> to be used in the prerequisite list?
sr> Other make implementation expands $* to the name of
sr> the target when listed in the prerequisites, but not gnu make.
No make expands $* in th
%% Sam Ravnborg <[EMAIL PROTECTED]> writes:
sr> deps_foo.o := foo.h
sr> foo.o : % : $(deps_%) bar.h FORCE
sr> @echo $^
sr> When executed I expected it to print:
sr> foo.h bar.h FORCE
sr> But it only prints bar.h FORCE
Right.
sr> Is it coorect behaviour that make does not
I'm having troubles using static patters.
See following example:
deps_foo.o := foo.h
foo.o : % : $(deps_%) bar.h FORCE
@echo $^
FORCE:
When executed I expected it to print:
foo.h bar.h FORCE
But it only prints bar
On Fri, Oct 03, 2003 at 11:01:02PM +0200, Sam Ravnborg wrote:
> I'm having troubles using static patters.
> See following example:
>
> deps_foo.o := foo.h
>
> foo.o : % : $(deps_%) bar.h FORCE
> @echo $^
>
> FORCE:
> ---
>
First, thanks for taking the time to respond some of the inquiries.
> >> where do you go when the user asks to go to "install"?
>
> am> Ho! I do not know. But it should not matter, we parse the
> am> makefile and provide the users with a list of the targets. In
> am> your example sh
"Paul D. Smith" wrote:
> Yes, not only in theory but in fact.
>
> But what I'm saying is that if you're providing a capability to jump to
> where a target is defined, you'll have to pick one of those. How do you
> choose which one? Or do you list the install target 3 times?
Not that I agree wit
%% "Alain Magloire" <[EMAIL PROTECTED]> writes:
>> where do you go when the user asks to go to "install"?
am> Ho! I do not know. But it should not matter, we parse the
am> makefile and provide the users with a list of the targets. In
am> your example should not the "install" targets be
10 matches
Mail list logo
