On Mon, Nov 2, 2015 at 3:22 PM, Gavin Cannizzaro <[email protected]> wrote:
> Hi Freddie,
>
> A belated thanks for this tip.
>
> I was able to get something working using this %<group> construct. It's a
> bit hackish (in my particular case), since I ended up merely echoing the
> value of %<group>, which somehow caused Tup to behave as I wanted. But I
> understand the difficulty with the underlying issue.
>
Is there a reason you can't use a bin to group the inputs to the final
rule? Something like:
: |> echo a > %o |> a.in {a-files}
: |> echo 1 > %o |> a--1 {a-files}
#: |> echo 2 > %o |> a--2 {a-files}
: {a-files} |> cat %f > %o |> %B.out
>
> The %<group> feature (as a command flag) is not mentioned in the manual.
> I think I have read everything in the docs (including journal.html!)---is
> there some documentation of how this works exactly?
>
Not yet :(. If there is not an issue for documenting it yet please feel
free to file one!
>
> Further to that... not being a C programmer myself, but being a great fan
> of Tup, is there some way that I can help with the project?
>
Thanks for your offer! What sorts of things are you interested in? One
thing that might be helpful is just going through the list of open github
issues and seeing if any can be closed because they've already been fixed.
I've been pretty terrible about updating github :(
-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.
