> bk> Implicit rules can handle multiple target patterns, is there any
> bk> reason static pattern rules couldn't also?
>
> The reason is that static pattern rules are shorthand for writing
> explicit rules, not longhand for writing implicit rules.
>
> That is, a static pattern rule is turne
Ted Stern <[EMAIL PROTECTED]> writes:
> You can reduce potential compilation cascades even further by
> ensuring that your *.gob processor compares previously existing
> output files against the new output and retains the original
> timestamp if no changes have been made.
This is a good examp
%% Britton Kerin <[EMAIL PROTECTED]> writes:
bk> I have a program gob2 which does this:
bk> some_file.gob -> {some_file.c some_file.h some_file-private.h}
bk> So I would like to be able to write this static pattern rule:
bk> # This rule says how to generate C files from GOB fi
On 13 Apr 2004 at 10:27 PDT, Britton Kerin wrote:
>
> I have a program gob2 which does this:
>
> some_file.gob -> {some_file.c some_file.h some_file-private.h}
>
> So I would like to be able to write this static pattern rule:
>
> # This rule says how to generate C files from GOB files.
>
I have a program gob2 which does this:
some_file.gob -> {some_file.c some_file.h some_file-private.h}
So I would like to be able to write this static pattern rule:
# This rule says how to generate C files from GOB files.
$($(MN)_GOB_GENERATED_FILES): %.c %.h %-private.h: %.gob
