W dniu 2014-08-11 17:52, stevek pisze:
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 haven't used variants, as this does not work on Windows, but without
variants the path printed is the path from root of project to the
Tupfile that has the executed command. This path is usually the path to
the source, as long as you compile the file with no path (so "gcc
main.c", not "gcc sub/folder/main.c").
From my point of view this is functionally identical to the way
recursive make works - instead of looking for these "entering"/"leaving"
messages, you have that info right in front of each command.
Regards,
FCh
--
--
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.
