Okay, I tested the executable provided above, and the recursive include worked perfectly.
With that said, it is no longer relevant as I have switched over to Tupfile.lua as per your suggestion. Related to that, what constitutes "change" with respect to Lua? I would initially think it would only consist of "exported" environment variable changes or changes to the rule resulting from tup.rule(...) (etc.). However, when I change something innocuous in one of the Lua files (e.g. add a space at the end of a line of Lua code), I sometimes get some outputs rebuilt (but not all outputs rebuilt or even all outputs that are derived from the Lua function in question--just "some outputs"). -Paul -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/tup-users/1d9748d3-25c6-4dcb-b6bb-5860b2506fd6o%40googlegroups.com.
