On 03/16/2015 08:35 PM, Ahmad Khayyat wrote:
If not, what else can I do?
This is probably one of the cases where trying to stick only to tup
causes only more trouble. Just use make to do exactly two things:
- generate some files usable for tup (so for example query the database
and write some temporary files for tup),
- run tup
At the end you can optionally commit some data to the database.
Tup has some limitations - you encountered several of them at once:
- files in hidden directories are not tracked as dependencies,
- files cannot be written to hidden directories,
- you absolutely cannot read and write to the same file.
I think the first two should be changed - the reasoning was to hide .tup
folder, so this limitation should be only for this particular folder.
The third one is fundamental to the way tup works and this can never be
changed (probably <: )...
That's why sometimes it's OK to use make to do some work before tup is
executed and after it finishes (; With tup's ^o flag you can even avoid
re-executing some commands if the timestamps of inputs changed, but the
contents didn't.
Regard,
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.
