I don't follow the question... why is execution tied to linking in your setup? Also, if each test is a separate executable, it sounds like your build is already extremely modular...
If your tests are generating a report file or something, you could add the running of each test as a rule that depends on the test executable (along with any other input data). If you are using some magic inside your application to run tests at dynamic link time, perhaps this would be cleaner... If you are trying to temporarily switch off building and running of the tests, you can use a configuration variable and ifdefs in your Tupfiles to add/remove them from your build... On Sun, May 25, 2014 at 7:22 AM, thegreendroid <[email protected]>wrote: > Will over-specifying all object files as inputs into the link step work? > > -- > -- > 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. > -- -- 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.
