No, as far as I know: it's a core Tup thing that processes can't read from their own outputs. The same happens with LaTeX (I say this because there are discussions about it around that might interest you). FWIW, my workaround for LaTeX builds is to keep "un-Tup-able" jobs out of Tup's sight and instead use some kind of script. Just an ugly hack, but there's really no way around it. With this approach, building becomes something like:
tup && bash finish-build.sh On the other hand, and while I don't know anything about Windows' linker's incremental linking in particular, techniques of this kind are often broken and end up giving headaches. Perhaps there's another thing you could try instead? -- -- 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.
