On Sep 28, 2006, at 3:23 PM, Randy J. Ray wrote:
That may or may not be enough to go on - please check back here if
you'd
like more assistance.
I had looked at those recipes (I should have mentioned that I did
due diligence
on reading all the docs before turning to the list's collective
wisdom). As it
happens, it leaves kind of open-ended the issue of actual make-
style actions
(that is, sub-processes versus just doing everything within Perl).
Yes, that's true. For better or worse, M::B actions are not as
declarative as make actions. Make actions are always text strings
(shell commands), whereas M::B actions are perl code. There's
nothing (except cross-platform compatibility) stopping a developer
from making that perl code call shell commands, though.
To actually execute an external command, you can use the
run_perl_script(), run_perl_command(), or do_system() methods.
There is no formal dependency mechanism in M::B between your *.xpl
files and their dependencies, so in the code that creates the .xpl
files you should explicitly use the up_to_date() method to check
whether any work needs to be done. Yeah, it would be nice to
decouple those like Make does, but we don't....
-Ken
