Spring RTS game engine VS xmake-repo

Seems the support would be a realistic feature, though, because it's based on https://springrts.com/ that does support MacOS X.

springrts: Designed for 3D rts games. May be worth looking into if that's what you're making. The site is kind of lack luster so I didn't do too much digging around.

...or Total Annihilation Spring, nowadays known as Spring RTS: https://springrts.com/

My current favorite is Beyond All Reason. Before BAR, my favorite was Zero-K. Both BAR and zk use the same game engine, SpringRTS. BAR and zk are very similar to one another, and they're successors for Total Annihilation and Supreme Commander.

Obligatory mention of another open source RTS engine (lineage tracing back to the original Total Annihilation): https://springrts.com/

Non-OSS Engine?

Total Annihilation for sure, the spiritual successor Supreme Commander is great but a bit too different for me. There's an open source recreation that's a bit rough to learn at first, but it's my favorite game of all time called Spring RTS. https://springrts.com/

The other thing is that if you're going to make an engine focused on rts games, you should probably study an existing RTS-focused engine. For example, here's the source code for Spring. Learn what it does, why, and how. You might decide this is good enough for what you want to do. You might decide this is pretty close, and you'll only want to extend it rather than start from scratch. You might decide to still start from scratch, but at least you learned something about requirements/ methods/ etc.

Pretty much any game on the Spring Engine (which Zero-K is on) will work on Linux.

xmake [1] gives you something like this via `xrepo env shell`.

[1] https://xrepo.xmake.io/

This project should also soon be available on xrepo, right now you can copy the headers or use the package in `package.lua` to install.

Yes, although the documentation seems bare-bones, the code looks clean.

The xmake package repository files might be useful also for people interested in making their own package manager, or even installing by hand.

Here is the package information for autoconf, for instance:

https://github.com/xmake-io/xmake-repo/blob/master/packages/...

It has download links, checksums for specific versions, and the Lua syntax seems easy to parse.

The package for NanoVG however, does not indicate anywhere that you need the GLEW and GLFW libraries:

https://github.com/xmake-io/xmake-repo/blob/master/packages/...

Therefore, if the official xmake-repo repository already provides the required package, you can use it directly without specifying the package namespace.

I written a c/c++ package manager https://xrepo.xmake.io/#/

Currently, we have included the following toolchain packages in the xmake-repo repository, allowing xmake to pull and integrate remotely:

Here's the github page for xrepo: https://github.com/xmake-io/xmake-repo