Compiling with Mono

• Mono 5.12.0 or greater
• MSBuild
• NuGet
• pkg-config

Environment variables

By default, SCons will try to find Mono in the Windows Registry on Windows or via on other platforms. You can specify a different installation directory by using the following environment variables for the respective bits option: MONO32_PREFIX and MONO64_PREFIX.

The specified directory must contain the subdirectories bin, include, and lib.

By default, the Mono module is disabled when building. To enable it, add the option module_mono_enabled=yes to the SCons command line.

Generate the glue

Glue sources are the wrapper functions that will be called by managed methods. These source files must be generated before building your final binaries. In order to generate them, first, you must build a temporary Godot binary with the options tools=yes and mono_glue=no:

scons p=<platform> tools=yes module_mono_enabled=yes mono_glue=no

After the build finishes, you need to run the compiled executable with the parameter --generate-mono-glue followed by the path to an output directory. This path must be modules/mono/glue in the Godot directory:

<godot_binary> --generate-mono-glue modules/mono/glue

This command will tell Godot to generate the file modules/mono/glue/mono_glue.gen.cpp. Once this file is generated, you can build Godot for all the desired targets without the need to repeat this process.

<godot_binary> refers to the tools binary you compiled above with the Mono module enabled. Its exact name will differ based on your system and configuration, but should be of the form bin/godot.<platform>.tools.<bits>.mono, e.g. bin/godot.x11.tools.64.mono or bin/godot.windows.tools.64.exe. Be especially aware of the .mono suffix! If you’ve previously compiled Godot without Mono support, you might have similarly named binaries without this suffix. These binaries can’t be used to generate the Mono glue.

• Do not build your final binaries with mono_glue=no. This disables C# scripting. This option must be used only for the temporary binary that will generate the glue. Godot will print a warning at startup if it was built without the glue sources.
• The glue sources must be regenerated every time the ClassDB-registered API changes. That is, for example, when a new method is registered to the scripting API or one of the parameters of such a method changes. Godot will print an error at startup if there is an API mismatch between ClassDB and the glue sources.

And Mono-enabled export templates:

If everything went well, apart from the normal output SCons should have created the following files in the bin directory:

• If you’re not linking the Mono runtime statically, the build script will place the Mono runtime shared library (monosgen-2.0) next to the Godot binary in the output directory. Make sure to include this library when distributing Godot.
• Unlike “classical” Godot builds, when building with the mono module enabled (and depending of the target platform), a data directory may be created both for the editor and for export templates. This directory is important for proper functioning and must be distributed together with Godot. More details about this directory in .

Examples

# Build temporary binary
scons p=windows tools=yes module_mono_enabled=yes mono_glue=no
# Generate glue sources
bin\godot.windows.tools.64.mono --generate-mono-glue modules/mono/glue
### Build binaries normally
# Editor
scons p=windows target=release_debug tools=yes module_mono_enabled=yes
# Export templates
scons p=windows target=release_debug tools=no module_mono_enabled=yes
scons p=windows target=release tools=no module_mono_enabled=yes

The data directory is a dependency for Godot binaries built with the mono module enabled. It contains important files for the correct functioning of Godot. It must be distributed together with the Godot executable.

The name of the data directory for an export template differs based on the configuration it was built with. The format is data.mono.<platform>.<bits>.<target>, e.g. data.mono.x11.32.release_debug or data.mono.windows.64.release.

This directory must be placed with its original name next to the Godot export templates. When exporting a project, Godot will also copy this directory with the game executable but the name will be changed to data_<APPNAME>, where <APPNAME> is the application name as specified in the project setting application/config/name.

In the case of macOS, where the export template is compressed as a ZIP archive, the contents of the data directory can be placed in the following locations inside the ZIP archive:

The name of the data directory for the Godot editor will always be GodotSharp. The contents of this directory are the following:

• Api (optional)
• Mono (optional)
• Tools (required)

The Mono subdirectory is optional. It can be used to bundle the Mono framework assemblies and configuration files with the Godot editor, as well as some shared library dependencies like MonoPosixHelper. This is important to avoid issues that might arise when the installed Mono version in the user’s system may not be the same as the one the Godot editor was built with. You can make SCons copy these files to this subdirectory by passing the option copy_mono_root=yes when building the editor.

The Api directory is also optional. Godot API assemblies are not bundled with the editor by default. Instead the Godot editor will generate and build them on the user’s machine the first time they are required. This can be avoided by generating and building them manually and placing them in this subdirectory. If the editor can find them there, it will avoid the step of generating and building them again.

The following is an example script for building and copying the Godot API assemblies:

Bash

Batch

DATA_API_DIR=./bin/GodotSharp/Api
SOLUTION_DIR=/tmp/build_GodotSharp
# Generate the solution
./bin/<godot_binary> --generate-cs-api $SOLUTION_DIR
msbuild $SOLUTION_DIR/GodotSharp.sln /p:Configuration=$BUILD_CONFIG
# Copy the built files
mkdir -p $DATA_API_DIR
cp $SOLUTION_DIR/GodotSharp/bin/$BUILD_CONFIG/{GodotSharp.dll,GodotSharp.pdb,GodotSharp.xml} $DATA_API_DIR
cp $SOLUTION_DIR/GodotSharpEditor/bin/$BUILD_CONFIG/{GodotSharpEditor.dll,GodotSharpEditor.pdb,GodotSharpEditor.xml} $DATA_API_DIR

set DATA_API_DIR=.\bin\GodotSharp\Api
set SOLUTION_DIR=%Temp%\build_GodotSharp
set BUILD_CONFIG=Release
# Generate the solution
.\bin\<godot_binary> --generate-cs-api %SOLUTION_DIR%
# Build the solution
msbuild %SOLUTION_DIR%\GodotSharp.sln /p:Configuration=%BUILD_CONFIG%
# Copy the built files
if not exist "%DATA_API_DIR%" mkdir %DATA_API_DIR%
for %%I in (GodotSharp.dll GodotSharp.pdb GodotSharp.xml) do copy %SOLUTION_DIR%\GodotSharp\bin\%BUILD_CONFIG%\%%I %DATA_API_DIR%
for %%I in (GodotSharpEditor.dll GodotSharpEditor.pdb GodotSharpEditor.xml) do copy %SOLUTION_DIR%\GodotSharpEditor\bin\%BUILD_CONFIG%\%%I %DATA_API_DIR%

The script assumes it’s being executed from the directory where SConstruct is located. <godot_binary> refers to the tools binary compiled with the Mono module enabled.

In the case of macOS, if the Godot editor is distributed as a bundle, the contents of the data directory may be placed in the following locations:

Command-line options

• module_mono_enabled: Build Godot with the Mono module enabled (yes | no)
• mono_glue: Whether to include the glue source files in the build and define as a preprocessor macro (yes | no)
• xbuild_fallback: Whether to fallback to xbuild if MSBuild is not available ( yes | no )
• mono_static: Whether to link the Mono runtime statically (yes | no)
• copy_mono_root: Whether to copy the Mono framework assemblies and configuration files required by the Godot editor (yes | no)