Thanks for responding. I had to do what you suggested to get this to work (moving rules to same Tupfile). If I understood right `tup' only supports referring to a generated file individually (by name) if it is generated in the same Tupfile. As my rules get complex it looks to me that it would getting harder to put everything in the same Tupfile. It would be interesting to know why a foreach on a group or a bin is not supported which would allow accessing them in other Tupfiles.
Thanks, Arun On Sunday, January 24, 2016 at 1:17:48 AM UTC+5:30, Andrew Jensen wrote: > Why not just do away with the Tupfile in a and reference the .c files > directly from the Tupfile in b: > > : foreach ../a/*.c |> gcc %f -c -o %o |> %B.o > > That works for me, but I'm running on Linux, not Windows, so you'll have > to adjust for your use. > > -Andy > -- -- 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.
