On Tue, Dec 22, 2015 at 6:04 PM, Freddie Chopin <[email protected]> wrote:
> Hi! > > I've tried the most recent tup few days ago and I must say that some things > broke for one of my projects. You may remember my post about a way to parse > any file with CONFIG_... variables with lua. I know that it's actually a > violation of "normal" tup's behavior and that I'm circumventing variants, > but > as long as configuration of variants can be placed only in subfolders > exactly > one level below root of project, then they don't really suit my needs... I > actually don't need variants - I just need a way to select one particular > configuration and use it as default for tup, as long as the user doesn't > "reconfigure" the whole project. And I'd really like to avoid any copying, > because then you have to remember which file to edit (the original or the > copy) to make any change. > > Fortunately it's still possible to parse the CONFIG_... variables directly > with lua and I hope that it will still be possible, otherwise the build > procedure of my project get's completely broken. Previously you could > actually > include the file with CONFIG_...="..." lines (only assignments with quoted > strings worked, but it was enough) and it worked fine. Now it always has > to be > parsed with the function I wrote, so this was not a big change. > > Hi Freddie, Can you put together a small test case for this? I'm not sure I fully understand the problem. I think the other issues you raised with the latest master are fixed, but I don't believe they are related to this. Thanks, -Mike -- -- 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.
