Yep, this is pretty key for me too. Tupdefault is really nice, but my directory structure looks something like:
TreeA FunctionA _inc FunctionA.h _src FunctionA.c _test TestA.c TestB.c TestC.c I can use Tupdefault in TreeA or above, but then I have to put empty Tupdefaults in every _test folder to "exclude" it, which is no more efficient than putting a TupFile in every _src folder. Recursive glob would make this trivial for me, where I can have one Tupfile in the top-level directory that does : foreach ./**/_src/*.c |> gcc -c %f -o %o |> %B.o You'd think the following would work, but Tup doesn't like it when _src doesn't exist in one of the folders. IMO it should ignore missing folders... : foreach _src/*.c |> gcc -c %f -o %o |> %B.o On Friday, June 30, 2017 at 7:42:32 AM UTC+2, [email protected] wrote: > > I'd like to be able to declare all files and sub-files and sub-directories > in a directory as dependencies. I'm writing software that compresses a > directory into a tar as part of the build system, and this feature would be > incredibly helpful to me. Where you can specify "dir/*" currently, I'd like > to be able to do "dir/**". > -- -- 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.
