1178
Comment:
|
1172
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
<<TableOfContents(3)>> == Introduction == |
== Introduction == |
Line 7: | Line 5: |
=== References === * '''!GitHub repository''': ''https://github.com/godotengine/'' |
=== References === |
Line 10: | Line 7: |
== Godot in Debian == | '''!GitHub repository''': ''https://github.com/godotengine/'' |
Line 12: | Line 9: |
=== Packaging Godot === |
|
Line 13: | Line 12: |
== Packaging Godot == | |
Line 24: | Line 21: |
== Packaging Godot games == | === Packaging Godot games === |
Line 35: | Line 32: |
---- CategoryGame | CategoryGameDevelopment |
Introduction
Godot is a multi-plaftorm game engine.
References
GitHub repository: https://github.com/godotengine/
Packaging Godot
The godot3 engine is being packaged.
Godot provides 3 binaries (and no libraries): the editor, the runner and the headless server.
The runner binary aka "export template" is close to an interpreter: it's called to run a .pck file that contains the game.
Godot integrates with other languages thanks to GDNative, which "bridges" between languages using a C API
The project can break compatibility on minor (but not patch) versions, hence packages are named godotX.Y godotX.Y-[runner|server]
Packaging Godot games
The source package for a game is built from the sources tar.gz as usual. Example for a game called "foo" that runs on godot3.1:
The binary contains the .pck file and a launch script e.g. /usr/games/foo and no server/runner, and it depends on godot3.1
The launch script contains:
/bin/sh /usr/bin/godot3.1 /usr/lib/godot3.1/foo.pck