Space Invaders

TLDR: Space Invaders clone implemented in C++ & OpenGL.

This is an ongoing project to learn C++, OpenGL, design patterns, build systems, testing and really anything that comes to mind. There are two branches that are always kept in a state that compiles: main and dev. The sprites used in this project are copied from Nick Tasios excellent guide to get started with Space Invaders and C++.

Requirements

• C++17 compliant compiler
• GNU Make
• Cmake version ~3.16 or greater
• OpenGL drivers
• GLEW. Tested with version 2.2.0

Building and running

Libraries

Make sure you have version 2.2.0+ of GLEW installed. If you are running a lower version, there are some artifacts even if the project compiles and runs. In addition to GLEW, this project needs to be compiled and linked against GLFW version 3.3+. It is recommended that you install this library as a shared library in your system.

Building

Cmake is used as the build system. There are scripts included in this repository that takes care of everything for you. If you don't have GLFW installed in your system or if its version is lower than 3.3, then cmake will pull the git submodule glfw and compile and link a static version when building.

There are 2 different build targets configured:

• Debug - The default target that also configures and builds the tests utilizing the Google Test framework.
• Release - Only configures and builds an optimized version of the game - nothing else.

foo@bar:space_invaders$ ./configure.sh [release]
foo@bar:space_invaders$ ./build.sh [release]
foo@bar:space_invaders$ ./run.sh [release OR -log]
foo@bar:space_invaders$ ./runtests.sh [ctest]
foo@bar:space_invaders$ ./cleanup [all OR release]

All the scripts will use the debug-target by default. With the debug-build you can use the flag -log to log to disk. If you wish to build and run a optimized version without the debugging symbols or tests pass the argument release without a dash to all the scripts. runtests.sh runs all the individual test-binaries. If you have ctest installed you can pass ctest as an argument to the script and it will run the tests with ctest and produce a nice overlook of all the tests.

The scripts will create a build-directory containing the different build environments. A bin-directory containing all the files, possible tests and resources needed to run the game will be created inside the build environments.

TODO

• Cleanup and improve the architecture of the codebase
• Add menu system & "normal" features
  • Higscores
  • Levels
  • Pausing and restarting
• Add various features
  • Whatever comes to mind, agile very much
  • Sound effects
  • Improve graphics
  • Improve gameplay