You can have rules without any outputs in tup. eg: foreach *.pdf |> dosomething %f |>
`dosomething` will be re-run whenever its input changes. I'm not sure how well this would work with an interactive program like a pdf viewer though, since it will be started in tup's "special" environment (chroot or whatever). On 26/11/15 14:29, Sanjoy Mahajan wrote: > In my makefiles for tex documents, I often use the following .PHONY > declaration and rule: > > .PHONY: %.xpdf > %.xpdf: %.pdf > xpdf $< > > Then 'make blah.xpdf' compiles to pdf (by a tex->pdf rule not shown > above) and starts the xpdf viewer using the rule above. > > Is there a way to do something similar in tup? It seems that tup > targets need to be actual files, so maybe not. > -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
