Best would be to disable caching — even if you figured out a portable way to specify the cache file path (cumbersome, as those are an implementation detail) and thus get going without Tup getting in the way (and that's assuming the compiler writes a single cache file for each compilation unit, which again is an implementation detail), you would get non-repeatable builds, which is one of Tup's goals.
-- -- 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.
