This Flatpak is not yet available on Flathub, but you can install it manually.
To download the file, you can use one of the following:
- Download manually - Use
this link, and download the
artifact called
Redot-x86_64.zip
. - Download using curl
curl https://github.com/chenasraf/org.redotengine.Redot/releases/download/v4.3-beta.1/Redot-x86_64.zip > Redot-x86_64.zip
Then, unzip it and install to flatpak from file:
unzip Redot-x86_64.zip
flatpak install --user Redot-x86_64.flatpak
Looking to package a Redot project as a Flatpak ? See flathub/org.redotengine.redot.BaseApp.
This Flatpak follows the latest stable Redot version. To update it, run the following command in a terminal:
flatpak update
This version of Redot is built with special
permissions
to be able to run commands on the host system outside of the sandbox via
flatpak-spawn.
This is done by prefixing the command with flatpak-spawn --host
. For example, if you want to run gnome-terminal
on
the host system outside of the sandbox, you can do so by running flatpak-spawn --host gnome-terminal
.
Redot expects the Blender executable to be named blender
(lowercase), so a script exactly named blender
that
executes Blender via flatpak-spawn --host
should be created. Below are two Bash
scripts which may need to be modified depending on your shell and
how Blender is installed.
#!/bin/bash
flatpak-spawn --host blender "$@"
#!/bin/bash
flatpak-spawn --host flatpak run org.blender.Blender "$@"
Make sure your script is executable using chmod x blender
. Use the directory path containing your script in the
Editor Settings (Filesystem > Import > Blender > Blender 3 Path).
This version of Redot is built with special permissions to be able to run commands on the host system outside of the sandbox via flatpak-spawn. This is done by prefixing the command with flatpak-spawn --host
. For example, if you want to run gnome-terminal
on the host system outside of the sandbox, you can do so by running flatpak-spawn --host gnome-terminal
.
To spawn an external editor in Redot, all command line arguments must be split from the commands path in the
external editor preferences and
because the command needs to be prefixed with "flatpak-spawn --host"
, the Exec Path is replaced by flatpak-spawn
and the Exec Flags are prefixed by --host [command path]
.
For example, for Visual Studio Code, where your external editor preferences would normally look like this...
Exec Path: code
Exec Flags: --reuse-window {project} --goto {file}:{line}:{col}
...it should look like this inside the Flatpak sandbox:
Exec Path: flatpak-spawn
Exec Flags: --host code --reuse-window {project} --goto {file}:{line}:{col}
For C#/Mono support, install org.redotengine.RedotSharp instead.Not yet supported.
Install Git, follow the flatpak-builder setup guide then enter the following commands in a terminal:
git clone --recursive https://github.com/chenasraf/org.redotengine.Redot.git
cd org.redotengine.Redot/
git submodule init
git submodule update
flatpak install --user flathub org.freedesktop.Sdk//24.08 -y
flatpak-builder --force-clean --install --user -y builddir org.redotengine.Redot.yaml
If all goes well, the Flatpak will be installed after building. You can then run it using your desktop environment's application launcher.
You can speed up incremental builds by installing ccache
and specifying --ccache
in the flatpak-builder command line (before builddir
).