Files
CodenameEngine/building
3b8859120f Use sh alternatives and fix change directory in building shell scripts (#769)
* Use sh alternatives and fix change directory in building shell scripts

The usage of the cd command in the shell scripts under building/ can
conflict at some point during the procedure. As far as I'm aware, it's
supposed to cd to the parent directory, but it does so strangely. On
some occasions, this may cause the directory to switch to /tmp
on Linux instead. This commit resolves that by instead using the
typical .. syntax, which is a shorthand for the parent directory of the
process.

Additionally, proper shebangs have been added that instead use
"/usr/bin/env sh", which returns the path to a suitable sh alternative:
that is, the closest program that can be found using 'sh' in the name.
This is one of the most recommended shebangs for a shell script, due
to 'env' typically being in the exact same position.

* Update cd in building shell scripts to use script relative path properly

The two prior versions would use the working directory's own parent
directory, not the script's. This commit simply makes it so that
changing the directory in the script uses its directory's parent instead.

* dont mind me

---------

Co-authored-by: ⍚~Nex <87421482+NexIsDumb@users.noreply.github.com>
2025-09-21 17:19:09 +02:00
..
2025-09-16 01:19:43 +02:00
2025-09-16 01:19:43 +02:00
2025-09-16 01:19:43 +02:00
2025-09-16 02:32:46 +02:00
2025-09-16 01:19:43 +02:00

Here's the full guide on how to setup and compile Codename Engine!

Open the instructions for your platform

Windows
  1. Install version 4.3.7 of Haxe.
  2. Download and install git-scm.
    • Leave all installation options as default.
  3. Run setup-windows.bat using cmd or double-clicking it and wait for the libraries to install.
  4. Once the libraries are installed, run haxelib run lime test windows to compile and launch the game (may take a long time)
    • ℹ You can run haxelib run lime setup to make the lime command global, allowing you to execute lime test windows directly.
Linux
  1. Install version 4.3.7 of Haxe.
  2. Install libvlc if not present already.
    • ℹ On certain Arch based distros installing vlc-plugins-all might solve if libvlc alone doesn't work.
  3. Install g++, if not present already.
  4. Download and install git-scm if not present already.
  5. Run setup-unix.sh using the terminal or double-clicking it and wait for the libraries to install.
  6. Once the libraries are installed, run haxelib run lime test linux to compile and launch the game (may take a long time)
    • ℹ You can run haxelib run lime setup to make the lime command global, allowing you to execute lime test linux directly.
MacOS
  1. Install version 4.3.7 of Haxe.
  2. Install Xcode to allow C++ app building.
  3. Download and install git-scm.
  4. Run setup-unix.sh using the terminal and wait for the libraries to install.
  5. Once the libraries are installed, run haxelib run lime test mac to compile and launch the game (may take a long time)
    • ℹ You can run haxelib run lime setup to make the lime command global, allowing you to execute lime test mac directly.

Tip

You can also run ./cne-windows.bat -help or ./cne-unix.sh -help (depending on your platform) to check out more useful commands!
For example ./cne-windows test or ./cne-unix.sh test builds the game and uses the source assets folder instead of the export one for easier development (although you can still use lime test normally).

  • If you're running the terminal from the project's main folder, use instead ./building/cne-windows.bat -COMMAND HERE or ./building/cne-unix.sh -COMMAND HERE depending on your platform.