> Previously someone mentioned the problem of finding folder of some > particular compilation step - this also shows that someone didn't even > try, as tup prints the folder (relative to project's root) in front of > EVERY command it executes. If there is no folder (no info at all), then > this means the command is run in the root of project. >
Well, sort-of. It prints the path to the variant folder, not the source folder. I don't see how one can in general tell whether a build variant is being used or not. Perhaps changing the output format slightly would be enough. I just did some experiments with the parallel case and it does seem that tup buffers up each commands output so thats a non-issue. Stephen. -- -- 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.
