Changes between Initial Version and Version 1 of Ticket #3729, comment 6


Ignore:
Timestamp:
Jan 23, 2016, 10:32:40 PM (8 years ago)
Author:
historic_bruno

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3729, comment 6

    initial v1  
    22> As for #1104, I don't understand the benefits of using CMake vs premake at this point. The original ticket points out that CMake supports XCode, but that's not a problem for premake either.
    33
    4 I haven't used Premake5 yet, but based on 4.x, I would say CMake is more stable, has a larger community of testers and users, supports more platforms "out of the box", and has more built-in potions. Premake's advantage is using Lua instead of the yucky scripts that CMake uses, but you end up having to write more logic to make up for what Premake lacks. Actually, I think newer IDEs come along more frequently than functional changes to our build system (our Premake version doesn't support clang, Xcode 4+, VS 2015 - to name a few).
     4I haven't used Premake5 yet, but based on 4.x, I would say CMake is more stable, has a larger community of testers and users, supports more platforms "out of the box", and has more built-in options. Premake's advantage is using Lua instead of the yucky scripts that CMake uses, but you end up having to write more logic to make up for what Premake lacks. Actually, I think newer IDEs come along more frequently than functional changes to our build system (our Premake version doesn't support clang, Xcode 4+, VS 2015 - to name a few).
    55
    66As a practical example, I'm building primarily *nix-oriented libraries with CMake in Visual Studio 2013, there's even an option that lets me set the platform toolset to v120_xp, but I could just as easily build them for 2015, 2012, 2010, 2008, or something older (or newer). That's just scratching the surface of the options available. The library devs don't have to write all those cases into their build system, they just have to support MSVC.