%% Harsha Kalidindi <[EMAIL PROTECTED]> writes: >> If you run "make install", then make says "OK, I need to build >> ../install/scripts/foo". It looks to see if that file exists. If it >> does, then VPATH is never consulted.
hk> We expect the above behavior. >> If it doesn't exist, then if VPATH is defined make uses it to try to >> find the target. hk> This is how it is working and it is still what we expect it to do. [...] hk> Does it look at the individual paths in VPATH plus the relative hk> targets (../install/scripts/foo, in this case) first or does it hk> look at just the relative targets from the directory of execution hk> first? I'm not exactly sure I'm understanding you: I explained it and you said this is what you expected... then asked how it works :). GNU make works exactly as I've described above: first it looks for the pathname exactly as it is given in the makefile. If that doesn't exist, _then_ it appends the pathname that is given in the makefile onto each entry in VPATH, in order, and looks for that. -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make