Hi.

I'm the author of teapot - http://teapot.nz/welcome/index and also 
interested in build tools.

Teapot uses a global DAG within reason - it's not possible to know how an 
external project builds itself.. but I've been thinking, at the very least 
I could track what files it installs to know it's specific outputs even 
though they are not described completely in the initial DAG.

A more concrete example would be - what headers does libpng install when 
running `make install`. Teapot supports invoking external build systems. 
But we don't know a lot about what outputs would be produced.

How does tup handle these situations?

Kind regards,
Samuel

-- 
-- 
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.

Reply via email to