Sample project / testbed for the https://github.com/Relintai/pmlpp pandemonium engine module.
Compile the engine itself, and then open the project inside the game folder.
After the initial import it might need an editor restart, however everything should work after that.
First make sure, that you have everything installed to be able to compile the engine. See the official docs or the official Godot docs for more info.
My setup/compile script uses the same tools, so you don't need to install anything else.
Now let's clone this repository:
git clone https://github.com/Relintai/pmlpp_standalone_sample
cd into the new folder:
cd pmlpp_standalone_sample
Now let's run the project's setup script, by calling scons without arguments.
scons
This will clone and setup the engine, and all of the required modules into a new pandemonium_engine folder inside the project, using http.
(If you want to use the github's ssh links append repository_type=ssh like scons repository_type=ssh)
Once it is done you can compile the engine.
To build the project on windows with 4 threads run the following command:
scons bw -j4
To build the project on linux with 4 threads run the following command:
scons bl -j4
I call this feature of the setup script build words. See.
Once the build finishes you can find the editor executable inside the ./pmlpp/bin/ folder.
For convenience there is a provided editor.sh, or editor.bat for running it from the project's folder.
These will create a copy, so you can even compile while the editor is running.
Alternatively if you don't want to use build words, you can also just go into the engine folder:
cd pmlpp
And compile godot as per the official docs.
The project's setup script contains support for "build words". These can be used from the root of this project.
For example to build the project for windows with 4 threads you can use:
scons bw -j4
The first argument must start with b (build), then it needs to be followed by a few abbreviations (the order does not matters)
The rest of the arguments will be passed directly to godot's scons script.
l: linux
w: windows
a: android
j: Javascript
i: iphone (Not yet finished, use build_ios.sh, and build_ios_release.sh)
Mac OSX: Not yet finished, use build_osx.sh
By default the system builds in release_debug.
Append d for debug, or r for release.
scons bwd -j4
build editor windows debug
scons bwr -j4
build windows release (this will build the windows release export template)
Append v to pass the vsproj=yes parameter to the build script. This will generate Visual Studio project files.
Append c to pass the compiledb=yes parameter to the build script. This is a new feature in 3.x to have this disabled by default to lessen compile times.
There are a few postfixes for the build words. These are more complex options. You have to append them to your build word with an underscore.
You can use as many as you want.
For example:
scons bl_slim_latomic -j4
With this postfix you can build a slimmed down version of the engine. This disables quite a few unneeded modules.
scons bel_slim -j4
If you get linker errors while building the game/editor about undefined referenced with atomic related functions you can use this postfix.
It will add the -latomic command line switch to the linker flags.
I ran into this issue while building on a raspberry pi 4 with the x11 platform. It might be related to the recent reworks to threading.
scons bl_latomic -j4
Appends debug_symbols=no to the build command, which will strip the resulting binary from debug symbols.
scons bl_strip -j4
In order to use scons cache and to tell the build system where some of the required sdks are located you usually have to use environment variables. Most of the time you might just want to add them globally, howewer this is sometimes unfeasible (e.g. you don't have administrator access, or you just want to have multiple sdk versions installed).
In order to solve this a build config file was added.
If you want to use the config simply rename the provided build.config.example to build.config, and customize
the settings inside.
If you you don't want to use the setup script (or just want to know what it actually does), this section will explain how to set everything up manually.
First clone the engine:
git clone https://github.com/Relintai/pmlpp
Now if you look at the HEADS file.
It contains the commit hashes for that particular revision for every module and the engine. The engine now contains all the modules, so at the moment only worry about the engine's commit hash.
You need to go and checkout the proper commit for it.
Now you can go ahead and compile the engine normally.
First pull the changes by calling
git pull orgin master
Then just run scons, to will update the modules.
Note: this is how to update the HEADS file. Normally you don't need to do this.
If you want to update the engine to the latest, you can use (action=update):
scons a=u
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent