Question: Create build script to make installation easier?

[plibither8]

Currently, users have to follow 6 steps to install and run 2048. Though these are small and can be done quickly, it would be much more convenient if we have a bash script that does this for us.

The bash script will do the following:

1. Clone the repository in the home folder.
2. mkdir build, cd build to create the build directory.
3. cmake .. and make to create the final, executable program.

These are the 3 main steps that the script will follow. After this, we should add the 2048 program to the PATH so that users can access the game from anywhere in their terminal.

Either adding to the PATH permanently or adding an alias to the game in their .bashrc or .zshrc files.

With the bash script we can also now handle OS specific actions, as adding to the PATH will be quite different in all the three major OSs.

[cawvyoct]

Humm, normally I only "run" programs listed in the releases section of a github project.

• One possibility is a statically-compiled program and then release it via the release section.
• Another possibility (which is a bit more verifiable) is using openSUSE Build Service to make the release for you [1].

[plibither8]

One possibility is a statically-compiled program and then release it via the release section.

Wouldn't there have to be a different compiled binary for each OS, platform and system architecture? If yes, then it's a bit too much of work IMO

[scivision]

This is handled by adding "install" section to CMake / Meson scripts.
Install is added in #91

Separately, if one wishes to distribute executables for multiple platforms in a GitHub Release, this can be easily done via Travis-CI deploy: statement.