%% Jason Pearce <[EMAIL PROTECTED]> writes:
jp> VHDL_SOURCES := $(wildcard *.vhd)
jp> vhdldep.mak : ${VHDL_SOURCES}
jp> perl vhdldep.pl -t mak ${VHDL_SOURCES} > vhdldep.makfail
jp> # sleep 1
jp> /bin/mv vhdldep.makfail vhdldep.mak
jp> include vhdldep.mak
jp> sources:: generated1.vhd
jp> generated1.vhd : generated1.vhd.m4
jp> m4 generated1.vhd.m4 > generated1.vhd.fail
jp> /bin/mv generated1.vhd.fail generated1.vhd
jp> sources:: generated2.vhd
jp> generated2.vhd : generated1.vhd.m4
jp> m4 generated2.vhd.m4 > generated2.vhd.fail
jp> /bin/mv generated2.vhd.fail generated2.vhd
Hm. If I understand what you're doing, I would avoid this two-step
operation by having the .mak file depend on the actual files. Does
something like this do what you want:
VHDL_SOURCES := $(wildcard *.vhd)
vhdldep.mak : generated1.vhd generated2.vhd ${VHDL_SOURCES}
perl vhdldep.pl -t mak *.vhd > vhdldep.makfail
/bin/mv vhdldep.makfail vhdldep.mak
include vhdldep.mak
generated1.vhd : generated1.vhd.m4
m4 generated1.vhd.m4 > generated1.vhd.fail
/bin/mv generated1.vhd.fail generated1.vhd
generated2.vhd : generated1.vhd.m4
m4 generated2.vhd.m4 > generated2.vhd.fail
/bin/mv generated2.vhd.fail generated2.vhd
?? I think it should.
Also, I would definitely use make variables for perl, m4, and /bin/mv
rather than writing them out directly... :-).
--
-------------------------------------------------------------------------------
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
_______________________________________________
Help-make mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-make
