What about explicitly copying the input files to the variant output 
directory? There are programs (that annoy build authors) such as latex that 
explicitly require that the input and output be in the same directory.  The 
current approach of pretending that the input files are in the output 
directory works, but it seems simpler to actually copy them there.  Then 
when you modify the "real" input files, there would be a rule to update the 
ones in the variant build, and that would trigger a rebuild in the variant. 
 It seems (to my naive self) like this implicit set of copy rules (combined 
with the configuration handling in the variant) would be all that is needed 
for variants to work.

David

On Friday, October 24, 2014 1:50:58 PM UTC-7, Ben Robinson wrote:
>
> I actually like that each variant is marked by a config file at the top of 
> the variant output directory.  It keeps each variant in a pocket universe 
> by itself, separate from all other variants, and from the immutable input 
> tree.
>
> And I like both how the tup files are stored in the input tree, and how 
> the rules are executed by first CDing into the corresponding output tree.
>
> The only current problem (as I see it), is that variants do not work on 
> Windows.  The reason for this is that the implementation is depending 
> heavily upon OS specific functionality, when it doesn't need to.  The file 
> access detection with FUSE is working, so you are correct, that needs to 
> stay.  But whatever variant logic is bugged, which is responsible for 
> implicitly mapping the input tree inside the output tree, can simply be 
> removed.  Simply replace the input expression in the rule with %I to 
> indicate explicitly that this input is in the input tree.
>
> So the proposal as stated still stands, and hopefully the implementation 
> implications are more clear.  Many thanks for your clarifications.
>
> Cheers,
>
> Ben
>

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