> > 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.
In our environment, murphy's law plays a big role. It's not at all uncommon to encounter developers with: * gigantic .login and/or .cshrc files * environment variables set that no sane person would ever want (eg, LD_LIBRARY_PATH, GCC_EXEC_PATH, etc) * they build out of repos in their home directory -- where their home directory is NFS mounted (which means significantly slower time to parse makefiles / build) Things were pretty bad when I joined this group. To combat the environment issues I ended up having to write a perl script to wrap build execution to strip down the environment & make it sane. I'm hoping I can do the environment fix-ups from within tupfiles or lua scripts. -brian On Wednesday, November 30, 2016 at 12:04:58 PM UTC-7, Erik wrote: > > 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] > <javascript:>> 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] <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.
