On 11/03/2014 11:01 PM, [email protected] wrote:
I think that what actually happens is that as it is parsing a Tupfile
that references a file that apparently doesn't exist, it pauses and
parses the Tupfile in that directory if it hasn't done so already, to
see if the file is generated. Hopefully it guards again circular
dependencies. There is a function "parse_dependent_tupfiles" in the
code. So it would appear that Tupfiles *do* in fact have dependencies.
You are right, I stand corrected.
I was aware of Tupfile dependencies on included and "run" files, and I
know that at least the Lua parser adds directory dependencies for
globbed directories, but I wasn't aware dependencies were added for
cross directory input files.
For the record, the error when circular Tupfile dependencies are
encountered looks like this:
tup error: Unable to parse dependent Tupfile due to circular
directory-level dependencies: sub
tup error [string "Tupfile.lua"]:1: Error while parsing dependent Tupfiles
--
--
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.
