On Sat, Feb 01, 2014 at 17:04:50 -0800, Matthew Borger wrote:
> 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.
It's not a Tup thing. It's something that a lot of tools on Windows
implement (particularly cl.exe, but gcc supports it as well). Basically,
you dump the arguments to a file (one per line usually) then execute it
with @argfile:
cat > argfile << EOF
-la
-lb
-lc
EOF
gcc @argfile -o prog prog.c
which will act like:
gcc -la -lb -lc -o prog prog.c
FWIW, Ninja supports "response files" (which is what the functionality
is called) as well by using "rspfile" in rule stanzas[1] which causes
Ninja to manage the response file itself instead of having the user know
that one is needed and make exceptions. This might be something Tup
could support with a flag (Maybe "^r"?).
--Ben
[1]http://martine.github.io/ninja/manual.html#ref_rule See "rspfile".
--
--
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.
