Grit alternatives and similar libraries
Based on the "Game Engine" category.
Alternatively, view Grit alternatives based on common mentions on social networks and blogs.
Godot9.9 10.0 L1 Grit VS GodotGodot Engine – Multi-platform 2D and 3D game engine
Cocos2d-x9.7 0.0 L1 Grit VS Cocos2d-xCocos2d-x is a suite of open-source, cross-platform, game-development tools used by millions of developers all over the world.
robotjs9.2 0.0 L4 Grit VS robotjsNode.js Desktop Automation.
GamePlay8.5 0.0 L1 Grit VS GamePlayOpen-source, cross-platform, C++ game engine for creating 2D/3D games.
Banshee Engine8.2 8.7 L1 Grit VS Banshee EngineBanshee Game Engine
Torque3D8.2 1.0 L1 Grit VS Torque3DMIT Licensed Open Source version of Torque 3D from GarageGames
Panda3D8.1 9.7 L1 Grit VS Panda3DPowerful, mature open-source cross-platform game engine for Python and C++, developed by Disney and CMU
Spring RTS game engine8.0 9.5 L1 Grit VS Spring RTS game engineA powerful free cross-platform RTS game engine. - Report issues at https://springrts.com/mantis/
CRYENGINE8.0 0.0 L1 Grit VS CRYENGINECRYENGINE is a powerful real-time game development platform created by Crytek.
Automagica7.5 0.0 Grit VS AutomagicaAI-powered Smart Robotic Process Automation 🤖
Polycode7.3 0.0 L1 Grit VS PolycodePolycode is a cross-platform framework for creative code.
Amazon Lumberyard7.2 2.3 Grit VS Amazon LumberyardAmazon Lumberyard is a free AAA game engine deeply integrated with AWS and Twitch – with full source.
AutoKey7.1 0.0 Grit VS AutoKeyAutoKey, a desktop automation utility for Linux and X11.
KlayGE7.0 6.3 Grit VS KlayGEKlayGE is a cross-platform open source game engine with plugin-based architecture.
flixel6.7 5.6 Grit VS flixelFree, cross-platform 2D game engine powered by Haxe and OpenFL
Allegro6.5 9.0 L3 Grit VS AllegroThe official Allegro 5 git repository. Pull requests welcome!
The MOAI Multi-platform Game Engine6.2 0.0 L2 Grit VS The MOAI Multi-platform Game EngineThis is the development repo of Moai SDK.
squirrel5.3 0.0 L1 Grit VS squirrelOfficial repository for the programming language Squirrel
Oxygine5.3 0.0 L1 Grit VS OxygineOxygine is C++ engine and framework for 2D games on iOS, Android, Windows, Linux and Mac
Torque2D4.9 6.1 Grit VS Torque2DA completely free, open-source, 2D game engine built on proven torque technology.
nCine4.8 7.9 Grit VS nCineA cross-platform 2D game engine
xmake-repo4.5 6.3 Grit VS xmake-repo📦 An official xmake package repository
ClanLib3.8 0.0 Grit VS ClanLibClanLib is a cross platform C++ toolkit library.
RaZ3.6 0.0 Grit VS RaZModern & multiplatform 3D game engine in C++17
Wolf Engine3.2 7.1 Grit VS Wolf EngineThe Wolf is a comprehensive set of C/C++ open source libraries for realtime rendering, realtime streaming and game developing
delta3dA robust simulation platform. [LGPL2]
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Grit or a related project?
This is the central repository for the Grit Game Engine project.
From here can be built the engine executable itself, the launcher, and various tools. These are mostly useless without the accompanying media tree (the Game Directory which is available on Sourceforge via Subversion. Therefore to get everything, execute the following:
git clone --recursive https://github.com/sparkprime/grit-engine.git grit-engine svn checkout https://svn.code.sf.net/p/gritengine/code/trunk grit-engine/media
The subversion tree also contains prebuilt up-to-date executables (Linux & Windows) so the majority of developers only need that. Grit can be substantially modified through Lua scripting, and this potential should be exhausted before modifying C++ code.
Build files are provided for Linux (
.../*grit.mk) and Visual Studio 2013 project
files. Building C++ takes about an hour on Windows and 10 minutes on Linux. Scripts are available
for copying new executables into Subversion, if it is checked out in the
Only Visual Studio Express 2017 is supported. The "Community" version is free (as in beer). Download it from the Microsoft site.
You will need the DirectX9 SDK (Google it), install that on your system (in
Program Files). The
install adds a system-wide environment variable
DXSDK_DIR pointing to the install directory. This
is used by the Visual Studio build. If Visual studio is running, you will have to restart it to make
it 'see' the new environment variable.
Open grit-engine.sln and build the whole solution with the Normal configuration. This will build all the tools and dependencies.
Debugging with Visual Studio requires the engine to be built with the Debug configuration. To run
in the debugger, execute the
engine project from inside Visual Studio. You may need to set the
working directory to the
media/ directory (from the
engine project properties).
Modifying the Build
The build uses hand-written MSVC build files. Each executable and library has a project file, and properties files are used to layer additional build options without duplicating them between project files. They are structured as follows:
grit-engine.sln: Collects together all the projects.
solution.props: Build options for all libraries and executables. Options that are the same for both Debug and Normal configurations live here.
solution_debug.props: Additional options when compiling in debug mode. Options that are the same for all object files live here.
solution_normal.props: Additional options when compiling in normal mode. Options that are the same for all object files live here.
pch.props: Options for enabling the precompiled header, used for top-level apps.
path/to/my-project/my-project.vcxproj: An executable or library to build. Build options that are specific to the library itself (like warning levels) live here.
path/to/my-project/my-project.props: Build options required by clients of a library and the library itself (typically defines and include paths).
The following instructions are for Ubuntu. If you're using another distro, you'll have to figure it out for yourself but hopefully the Ubuntu instructions will help. Note that the make files require GNU make, which may be called gmake on your system.
sudo apt-get install subversion g++ make pkg-config gdb valgrind \ libfreeimage-dev libzzip-dev libfreetype6-dev libglu1-mesa-dev \ libxt-dev libxaw7-dev libglew1.5-dev libxrandr-dev \ libgoogle-perftools-dev libopenal-dev libreadline-dev freeglut3-dev \ nvidia-cg-toolkit libvorbis-dev xutils-dev libicu-dev
make -j 8 in the root (adjust for your number of cores) will build everything.
Executables for the current platform are left in the root directory. You can add it to your PATH.
You can debug Grit with
valgrind. If the assembly is too obscure, disable optimizations
by overriding the OPT variable as so:
make -j 8 OPT=
Note that this will not rebuild anything that is already built, so you might want to first delete specific object files -- the ones containing the code you're debugging, and then rebuilding them without optimizations.
Modifying the Build
The makefiles are handwritten. They use a lot of GNU make specific features. Each sub-project and
dependency defines a
grit.mk file which defines the additional source files and required build
options. These are all included by the root
Makefile which computes the actual build rules.