gabry/CodenameEngine
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
4d84e65cb50477829bdab2b921650e6d812266a1
CodenameEngine/building
T
History
Yoshman29GitHubHEIHUAaFrakitsKolze
 4d84e65cb5 flixel-animate implementation (#893) 
* added flixel-animate to libs

* I BROKE THE OFFSETS FUCK

.

* yes it does blehtty wdym??

* Removed flxanimate entirely + Fixed transition + Fixed offsets

* Deleted caches (relaunching actions)

* frameOffset for atlases (need testing)

* useRenderTexture added to xml

* Fixed atlases for mods

* a simple redirect so old mods wont break that badly (#879)

* Update FunkinSprite.hx

* remove trace

* Fixed ghosts for atlases

* usable character editor (not entirely fixed)

* fixed zoomFactor + temp fix for atlas popping

* early structure for character editor atlas anim display

* zoomFactor for atlases

* Animate Atlas character editor previews

* FlxAnimateSettings specification

* fixed animation swapping on atlas characters

* OH YEA BABY NEW FLXANIMATE UPDATE THAT MADE CODE 50X SIMPLER **AGAIN** 💖 /pos

* Added label checkbox in Character Editor

* Fixed culling issues with FlxAnimate (fr this time)

* fixed some atlases

* HOW THE FUCK

* gf sad fix + AliasMacro (for backwards comp, manual impl for now)

* Fixed pop-ins

* Update Character.hx

* applyStageMatrix

* FlxAnimate pull request merge (empty commit)

* flixel-animate** i'm clumsy asf i meant the lib not the class name fuck

* Update libs.xml

* Merge changes from main (#892)

* repair ScriptableShader.shader = null (#877)

* optimize updateInput (#878)

* optimize updateInput

* resize optimize

* __notePerStrum optimize

* Update StrumLine.hx

* NoteGroup optimize (#881)

* NoteGroup optimize

* CoolUtil.bound faster

* makes commit with github desktop W FRAKITS

* Use fastSinCos for notes (#889)

* Update Strum.hx

* Update Strum.hx

---------

Co-authored-by: HEIHUAa <112499486+HEIHUAa@users.noreply.github.com>
Co-authored-by: Frakits <90983918+Frakits@users.noreply.github.com>

---------

Co-authored-by: Kolze <53307233+KolzeYT@users.noreply.github.com>
Co-authored-by: HEIHUAa <112499486+HEIHUAa@users.noreply.github.com>
Co-authored-by: Frakits <90983918+Frakits@users.noreply.github.com>
2026-01-28 20:29:32 +01:00
..
alsoft.txt
Update Audio Backend from Vs Camellia v2.75.1 (info at desc)
2025-11-16 15:22:58 +07:00
cne-unix.sh
Use sh alternatives and fix change directory in building shell scripts (#769)
2025-09-21 17:19:09 +02:00
cne-windows.bat
finally doing this
2025-09-16 01:19:43 +02:00
generate-docs-unix.sh
Improve documentation generation scripts and guide (#814)
2025-12-23 03:13:21 +01:00
generate-docs-windows.bat
Improve documentation generation scripts and guide (#814)
2025-12-23 03:13:21 +01:00
libs.xml
flixel-animate implementation (#893)
2026-01-28 20:29:32 +01:00
README.md
opa
2025-12-23 03:21:48 +01:00
setup-unix.sh
Use sh alternatives and fix change directory in building shell scripts (#769)
2025-09-21 17:19:09 +02:00
setup-windows.bat
finally doing this
2025-09-16 01:19:43 +02:00

README.md

Compiling Codename Engine

Do you want to turn your source code into a playable build to play? Then you want to compile the source code, follow this guide.

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.

Generating Codename Engine's API documentation

Mainly recommended if you intend to fork the engine and make your own custom version to publish.
Do you want to generate an API documentation so people can understand and mod your playable build? This documentation can be uploaded to your website.
If you just want to compile the engine normally for your hardcoded mod or for yourself you can skip this step.

Select your platform to continue.

Windows
  1. Run generate-docs-windows.bat using cmd or double-clicking it and wait for the doc.xml to be generated inside the docs folder.
MacOS/Linux
  1. Run generate-docs-unix.sh using the terminal or double-clicking it and wait for the doc.xml to be generated inside the docs folder.
  1. You can use this doc.xml file to generate a full HTML documentation (that you can open in your browser for example) using Haxe's dox generator; check Codename Engine's webiste for example.

Caution

The doc.xml might contain some sensible paths of your computer: make sure to filter the file before publishing it for everyone if you want to keep those paths private!
To filter and delete those paths, you may use Codename Engine's website's doc filter Python script by simply running it in the same folder of your doc.xml file. This script will also delete everything irrelevant to the engine that was generated in your documentation, such as libraries' (like OpenFL or Flixel) APIs.

Reference in New Issue View Git Blame Copy Permalink