When comparing Jam vs CMake, the Slant community recommends CMake for most people. In the question“What are the best open-source build systems for C/C++?” CMake is ranked 2nd while Jam is ranked 15th. The most important reason people chose CMake is:
This way everyone can use their favorite IDE in order to develop CMake, Code Blocks, qtcreator, Visual Studio, (and more).
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Has a central package repository
A central repository provides more guarantees about the availability of the package. With requiring directly from repository urls, the entire project could potentially be taken down on a whim.
Pro Community is focused on client side javascript
Because Jam only manages Javascript and only works on the client side, you have the assurance that any packages listed are AMD compatible for asynchronous loading.
Pro Architecture independent
Jam's only a front-end package manager, the rest of your server can be on a different architecture or framework. No matter what the architecture, Jam will integrate easily with it.
Pro Provides the best AMD compatibility allowing for better asynchronous loading
Jam requires AMD (Asynchronous Module Definition), which means faster package loading, as it can be done asynchronously.
Pro Compatible with different IDE's
This way everyone can use their favorite IDE in order to develop CMake, Code Blocks, qtcreator, Visual Studio, (and more).
Pro Built-in, cross-platform dependency finding
Pro Out-of-the-box GUI available
CMake comes with the fantastic ncurses GUI ccmake
out of the box. Large codebases including WeeChat use it, to the point that the developer never needs to touch CMake code, but it is highly readable if he wishes to examine it.
Cons
Con Forced AMD compatibility means fewer libraries
AMD is currently not as popular as CommonJS modules, which means if a library isn't supported, you'll have to deal with it yourself.