1) You can use bash instead of sh by prefixing your command with ^b^. Note
this will run with pipefail enabled.

2) The only performance impact that I can see is that if you update a tup
file, tup only has to reparse the ones that changed. If it's one giant
file, it will always have to be reparsed if touched. However, I doubt this
will ever be a significant source of update time. However, I'm not an
expert so others might have more to say.

On Wed, Nov 30, 2016, 10:08 Brian Vandenberg <[email protected]> wrote:

> Will doing something like this negatively affect tup's update time?  That
> is to say, is there anything multiple Tupfiles provides that makes "tup
> upd" superior -vs- an essentially monolithic Tupfile?
>
> -brian
>
>
> On Wednesday, November 30, 2016 at 1:59:29 AM UTC-7, Freddie Chopin wrote:
>
> On Tue, 2016-11-29 at 07:41 -0800, Brian Vandenberg wrote:
> > How can I get tup to build from a common root (that is, not switch
> > directories to where each tupfile is)?
>
> You cannot do anything more than have a single Tupfile in the common
> root. In the subfolders you can however have some special files (with
> build description of these subfolders) which can be included manually
> by the top-level Tupfile.
>
> Regards,
> FCh
>
> --
> --
> 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.
>

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