On Sat Dec 15 00:39:19 2007, [EMAIL PROTECTED] wrote: > If you modify one of the Perl modules that turns .pmc files into .c files, > then run make again, nothing happens. The .pmc rules should each have a > dependency on the appropriate .pm file. > > This task requires a minor amount of Perl knowledge and some Makefile > knowledge. It should take less than an hour to complete.
The .c files (the generated files) should have the dependency on the tool, not the .pmc files; then, the tool should depend on each Parrot:: module it uses, and each of them should depend on the modules they use... Any .pl -> .pm or .pm -> .pm dependency is just a $(TOUCH) , a do nothing that will allow us to regenerate the C if any of the modules used changes. We can then update the makefile generation process to automatically ferret out the .pm/.pl relationships at config time as best we can by searching for 'use ...'. Then the generated C files can just have a sole dependency on the .pl that created them. (And then we can do something similar with the ops C files.)
