This succeeds in building the targets, but only because when it looks for either of the files, both are created.
This causes problems at the end, when gmake deletes all intermediate files. Because it didn't generate some of them, they just appeared (in the case of one of the .c files - produced from applying the rule to a required getopt header), then gmake thinks that it existed all along, and so it doesn't delete the file upon completion. I know it's a really picky case, but if these generated files end up lying around, they will get checked into the source repository... Thanks, Kev. On 11:58, Kevin Musker wrote: > Probably better belongs on a gmake list... but... > > This isn't possible with an implicit rule though is it? > > For example: > > %.h %.c: %.ggo > gengetopt ... Sure it is, just try :) Andre -- The only person who always got his work done by Friday was Robinson Crusoe (See attached file: signature.asc) _______________________________________________ Help-gengetopt mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gengetopt
signature.asc
Description: Binary data
_______________________________________________ Help-gengetopt mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gengetopt
