Thanks for catching the typo. This is least amount of script i wrote for any build tool! Beats make, scons, fabricate on Windows.
Excited so far looking at the speed of incremental builds. Kudos to the Creator and active user community. On Saturday, February 17, 2018 at 6:39:22 AM UTC-5, Guillaume Maudoux (Layus) wrote: > > From my smartphone here, but I think you want !cc, not $cc. > > Le 17 février 2018 11:36:25 UTC+01:00, satish krosuru <[email protected] > <javascript:>> a écrit : >> >> run is not supported on Windows 10. So i wrote a script to output the >> rules for each file in source tree. >> However I get an error on the third line 'Attempted to add duplicate >> command ID' >> It is the same error even if i remove foreach. >> >> include_rules >> : foreach dir1/dir2/file1.c |> $cc |> >> : foreach dir1/dir2/file2.c |> $cc |> >> >> >> On Friday, February 16, 2018 at 11:39:42 AM UTC-5, [email protected] >> wrote: >>> >>> On Thu, Feb 15, 2018 at 10:57 PM, satish krosuru <[email protected]> >>> wrote: >>> > Thanks Erik. Didn't realize that it is possible to insert rules at >>> runtime >>> > using run. >>> > I can use script to generate Tupfile explicitly listing each file. >>> >>> I would recommend staying away from a run script if possible. They may >>> be removed in the future in favor of just having the built-in Lua >>> support and built-in Python support (as well as the original Tupfile >>> support). Although you could of course continue to use a version of >>> tup that supports them. I don't have a definite timeline for this, >>> though. >>> >>> I do agree with Erik's other suggestions - renaming files or putting >>> problematic files into a different directory so that you could just >>> list *.c would be ideal I think since your build logic would be much >>> more simplified (compile everything in these directories, then link >>> everything is much easier to understand). If that really is not >>> feasible, listing files explicitly or using the Lua parser for >>> filtering is probably your best bet. >>> >>> -Mike >>> >> -- -- 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.
