On Mar 15, 2012, at 5:23 AM, Konstantin Tokarev wrote: > For my use cases they will be default (e.g., Qt support requires at least 6 > build > rules). Also remember that build rules can be used to implement support for > programming languages other than C/C++, code generators, and preprocessors.
Could you do me a favor and convert a few of your Qt build rules to this new syntax (or some variant of it), and post them to the build rules wiki page? It would be good to have those available as I work through the implementation. >> The way you've described it, the system has to detect that >> "rule.compiler" accesses some context data, while "if not >> rule.flags.DebugInfo then return "-s" end" is a Lua chunk with its own >> return statement. This requires that Premake actually *parse* the text >> within the %() segment to figure out if it's just accessing context data >> (something that you can prepend "return context." to and get a valid Lua >> chunk) or an actual Lua chunk to be executed. > > I think it will always load chunk. Jason: could you clarify this? Jason McKesson is right here, there would need to be some differentiation, otherwise you would always have to write $(return cfg.objdir) instead of $(cfg.objdir). -st. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Premake-users mailing list Premake-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/premake-users
