I've been using Tup for a while, and I've found it to be fantastic! Here's my problem:
I recently started using flycheck with emacs. It creates (what it claims to be) temporary files in the same directory as the source code but prefixed with flycheck_. i.e. a file called My_Class.cc would have a file called flycheck_My_Class.cc. This, of course, wreaks havoc with my simple build rules (using the legacy parser) which were essentially: : foreach *.cc |> !cc |> I guess I can break the problem into 2 parts: - Test classes: these all have the naming convention: Test.<class name>.cc - Regular(?) classes: there is no common designation at the beginning of each class. Test classes are fixed simply with a change to the rule: foreach Test.*.cc ... Can someone offer a suggestion as to how to address the rest of the classes? I am open to using the lua parser, but would need help migrating my rules over to the new system. Thanks for your help, Shmuel -- -- 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.
