Hi! I've only started using tup in the last two days, but the great dev experience has convinced me to give it a harder try for our problem. In our project we're experimenting with abstracting away the build system (generating the tupfile under the hood as an implementation detail).
The end dev might add/remove files from nested directories (so a single flat wildcard won't do). The corresponding rules should be added/removed from tupfile automatically. Third party dependencies might also be added/removed (they resize in their respective directory, inside a known directory at the current project's top level), rules for each dep are recursively generated in the above fashion and inserted into the one top level tupfile. We're currently doing a naive `find` to discover new files inside the top level project & new deps, and regenerating the tupfile. The scan becomes the bottleneck. Is there a way to hook into tup so that only added/removed top project rules/deps rules are generated? We can't use the watcher because this needs to work on OS X & Windows. Also, ideally the only command to run is "tup", but since we're abstracting away we can compromise here. Any help would be appreciated. Thanks! -- -- 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.
