Is it also possible to add entries to a group with the syntax of adding 
entries to a variable?

# add additional library
$(ROOTPATH)/Out/<LIBS_TC> += $(LIBS_CTC_621)



Am Mittwoch, 8. August 2018 15:01:44 UTC+2 schrieb Guillaume Maudoux 
(Layus):
>
> Hi Gernot,
>
> Answers below in the mail, plus a complete example here:
>
> $ cat Tupfile  
> :               |> touch %o         |> a            | test/<all>
> :               |> touch %o         |> aa           | <all>
> :               |> touch %o         |> b            | {all}
> :               |> touch %o         |> c
> :               |> touch %o         |> d
> # does not work, empty commands can only be used to add files to a bin, not a 
> group
> : c             |>                  |>              | <all>
> : d             |>                  |>              | {all}
>
> : {all}            |> echo %f     > %o |> bins.txt
> : test/<all>       |> echo %<all> > %o |> groups1.txt
> :            <all> |> echo %<all> > %o |> groups2.txt
> : test/<all> <all> |> echo %<all> > %o |> groups3.txt
>
> $ tail *.txt   
> ==> bins.txt <==
> b d
>
> ==> groups1.txt <==
> a
>
> ==> groups2.txt <==
> aa
>
> ==> groups3.txt <==
> aa a
>
> — Layus.
>
> On 08/08/18 11:00, Gernot wrote:
>
> Hello,
>
> seems it's not so easy so maybe some easier questions:
>
> How can I add manually something to an existing group 
> ($(ROOTPATH)/Out/<LIBS_TC>)?
>
> : |> the command that builds something |> something | 
> $(ROOTPATH)/Out/<LIBS_TC>
>
> How can I pass the contents of this group to an external script?
>
> : | $(ROOTPATH)/Out/<LIBS_TC> |> script %$(ROOTPATH)/Out/<LIBS_TC> |> ...
>
>
> Thanks,
> Gernot
>
>
> Am Montag, 23. Juli 2018 15:24:58 UTC+2 schrieb Gernot: 
>>
>> I have a question regarding tup build sytem:
>> When there are multiple inputs to one command/macro, how is it possible 
>> to access a specific input parameter?
>> In Windows batch for example it is possible just using %1, %2 and so...
>>
>> For example:
>>
>>     $(ROOTPATH)/Cfg/Application.lsl $(ROOTPATH)/Out/<LIBS_TC> |> 
>> !scriptltc621 |> $(ROOTPATH)/Out/Link.cmd {BUILD_SCRIPTS}
>>
>> In the macro scriptltc621 some fixed stuff and also the parameter 
>> Application.lsl is writting to the output file.
>> Now, all the libraries from group <LIBS_TC> should also be written to the 
>> output file but only the basename (%b) of each file of the group.
>>
> -- 
> -- 
> tup-users mailing list
> email: [email protected] <javascript:>
> unsubscribe: [email protected] <javascript:>
> 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] <javascript:>.
> For more options, visit https://groups.google.com/d/optout.
>
> ​
>

-- 
-- 
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.

Reply via email to