The tup manual says that the groups are directory specific and I see the following example mentioned to highlight the point.
#./submodules/sm1/Tupfile : foo.c |> gcc -c %f -o %o |> %B.o ../<submodgroup> #./submodules/sm2/Tupfile : bar.c |> gcc -c %f -o %o |> %B.o ../<submodgroup> #./project/Tupfile : baz.c | ../submodules/<submodgroup> |> gcc -c %f -o %o |> %B.o I am trying to understand how groups being directory specific helps. Wouldn't a system based on unique group names alone have worked -like the following? #./submodules/sm1/Tupfile : foo.c |> gcc -c %f -o %o |> %B.o <submodgroup> #./submodules/sm2/Tupfile : bar.c |> gcc -c %f -o %o |> %B.o <submodgroup> #./project/Tupfile : baz.c | <submodgroup> |> gcc -c %f -o %o |> %B.o Can someone explain how groups being directory specific helps ? Thanks, Arun -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/tup-users/2a44c8f4-eebb-4007-bdfa-73ad734c5888%40googlegroups.com.
