Hello all, Context: For the last couple years our project has had the luxury of not needing to use variants (or build configuration) at all, but that is no longer the case. (We have some ARM/Beaglebone code that partially shares enough code with our Intel/x64 code that it makes sense for them to be in the same project).
Is there an elegant way to recursively limit an existing subtree to only build with certain variant? Or should I just bite the bullet and add ifdefs to all 50+ Tupfiles? I may just bite the bullet and hack up a shell script that adds the switches, but maybe there is a more elegant way... I am imagining something along the lines of conditionally undefining all macros and variables in the Tuprules file in the subdirectory, although I doubt that would work... or perhaps it would be legal (or could be made legal) to put an ifdef in a Tuprules file without a trailing endif statement... Cheers, Andrew -- -- 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.
