As for configuration building code in general, I'd like you to consider one special use case.
In my Qt Creator plugin I use Premake itself for project parsing. Actually, I'm running specific action, defined in Lua file, which is inserted by plugin into Premake's Lua state. When project settings are changed in GUI, or premake4.lua is modified, I need to re-parse project; however, I don't need "backing" of every field. There are some groups of fields 1) includedirs, defines - need to be refreshed when a) user changes toolchain, active Qt version, or Premake arguments; b) premake4.lua or any file it loads changes 2) files, configurations, vpaths, debug* - need to be refreshed only when premake4.lua or any file it loads changes 3) other properties are used only when generating project files I believe that building only a part of configuration could save some CPU cycles when refreshing project data, especially for large solutions. -- Regards, Konstantin ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Premake-users mailing list Premake-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/premake-users
