7 comments

3

Another one? I still don't see why I would use anything but make.

I've tried Scons because someone wanted to contribute it to a project I was working on. I don't like it. It uses Python so it has Python's failings and I don't really understand any of what it does. I was going to try Premake but I could not see how to create my own recipes making it utterly useless if you aren't all C/C++/C#. I don't even think you can mix the languages in one project.

I'll look at this one and see.

0

Our sentiments are similar. The readme contains the obligatory:

It is similar to cmake, automake, premake, but more convenient and easy to use.

Of course anyone can claim that, but we can't really know until we try it ourselves. Next time I start a new project and have the luxury of being able to inject a new tool into the ecosystem I'm going to try it out and see.

2

It is similar to cmake, automake, premake, but more convenient and easy to use.

https://xkcd.com/927/

0

lol. Appropriate.

2

Oh gooooood. More prerequisites to install because devs couldn't stick to make.

0

Because writing a new build system appears easier than learning how to use the existing ones.

0

I don't get the point of this. I use vanilla gnu make in all my projects. I have a solution make file that builds all the other makes files. I compile C/C++, Java, Python, Dot Net projects, run unittests, and build zip packages and auto deploy into my test environments all with gnu make.

And I promise you I could compile any other language that has a command line interface too... gnu make runs on every platform because its written in C.

I think this xmake thing is just a waste of time.