Could you provide an example of the @arg thing? All I can see form the tup manual is that @ is used for variables from the tup.confg file. I could have tup generate a shell script to use with the rules to reduce the command line length but that seems pretty hacky.
On Friday, January 31, 2014 3:36:51 PM UTC-8, Ben Boeckel wrote: > > On Fri, Jan 31, 2014 at 08:42:47 -0800, Matthew Borger wrote: > > I'm building a cross platform application. Tup works great on linux but > > when I try to run it on Windows (XP 32-bit) I get the following error. > It > > has to do with the length of the command, not the file size like the > error > > says. I found that if I shorten the command then tup works fine. Is the > > command length a limitation on Windows, and if so, does anyone know of a > > workaround? > > Usually you dump the arguments to a file then do the response file > argument thing on the original command (@argfile). > > --Ben > -- -- 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/groups/opt_out.
