and implement local caching, like ccache but supporting msvc as well as gcc/clang (actually msvc might be disabled at the moment)
… likewise remote caching, like Mozilla’s sscache for teams (again supporting msvc/gcc/clang)
it has its own package manager but also works with pretty much all other popular package managers
the build system will default to any matching installed system libs unless you say otherwise ({ system = false} on a per-included package basis)
it downloads and installed necessary packages when first building a project
package manager can use pre-compiled Windows artefacts
can use the hosted online repo, or our own online or local repos (multiple if we want)
location of alternative repos can be set in xmake.lua file or configured on command line (or config file).
can configure project with a TUI menu xmake f --menu
It just feels more straightforward and logical to me too. I know that’s subjective, but the objective part of that is it’s a unified build system, cache system and package manager that sets out to work with other tools.
it’s a build system itself, it doesn’t need make or whatever and compilation speeds are similar to ninja – which means it can do things like distributed building – and implement local caching, like ccache but supporting msvc as well as gcc/clang (actually msvc might be disabled at the moment) – … likewise remote caching, like Mozilla’s sscache for teams (again supporting msvc/gcc/clang)
So it offers nothing over cmake, and at best it matches features already offers for ages, such as transparent support for compiler cachês and distributed compilers.
it has its own package manager but also works with pretty much all other popular package managers –
That lies somewhere between matching cmake’s features, and placing users in a losing proposition with its own package manager.
can configure project with a TUI menu xmake f --menu
Not only is this irrelevant but it is also something cmake provides.
Also, cmake is the de facto standard and supported natively by IDEs such as Visual Studio.
xmake is just nicer, more concise and 100% less shouty. People in general use cmake because it’s the de facto standard, not because they like cmake and its DSL.
xmake can generate cmake files too so it’s not going against the grain. There are plugins for popular IDEs as well.
xmake is just nicer, more concise and 100% less shouty.
Not really. It’s yet another build system whose main aspiration is to eventually match cmake’s capabilities but missing all the reasons that made cmake the de facto standard, such as the declarative straight to the point way of specifying targets.
Close to half of C++ developers in that survey regularly use something other than CMake and I’ve seen projects at Microsoft and Epic Games use xmake. Why are you being such a pecker?
I’ll give some bullet points that might be of interest, I agree that they need a funky infographic or similar.
it’s a build system itself, it doesn’t need make or whatever and compilation speeds are similar to ninja
it has its own package manager but also works with pretty much all other popular package managers
{ system = false}on a per-included package basis)can configure project with a TUI menu
xmake f --menuIt just feels more straightforward and logical to me too. I know that’s subjective, but the objective part of that is it’s a unified build system, cache system and package manager that sets out to work with other tools.
(edited: tidied bullet lists)
So it offers nothing over cmake, and at best it matches features already offers for ages, such as transparent support for compiler cachês and distributed compilers.
That lies somewhere between matching cmake’s features, and placing users in a losing proposition with its own package manager.
Not only is this irrelevant but it is also something cmake provides.
Also, cmake is the de facto standard and supported natively by IDEs such as Visual Studio.
Knowing this, why would anyone bother with xmake?
In your opinion, I’d say the overall integration and being an actual build system are offerings for starters.
It also supports other languages like Zig, Pascal and Rust too. Here’s an example of C++ calling Rust, note the easy inclusion of Cargo crates…
https://github.com/xmake-io/xmake/tree/dev/tests/projects/rust/cxx_call_rust_library
xmake is just nicer, more concise and 100% less shouty. People in general use cmake because it’s the de facto standard, not because they like cmake and its DSL.
xmake can generate cmake files too so it’s not going against the grain. There are plugins for popular IDEs as well.
Not really. It’s yet another build system whose main aspiration is to eventually match cmake’s capabilities but missing all the reasons that made cmake the de facto standard, such as the declarative straight to the point way of specifying targets.
And yet lots of people use xmake and other alternatives…
Define “lots”.
Also, your weekend pet project is not the same as a corporation’s cash cow.
Close to half of C++ developers in that survey regularly use something other than CMake and I’ve seen projects at Microsoft and Epic Games use xmake. Why are you being such a pecker?