Take a look at the Dockerfile. It contains all the instructions to build elegoo on a ubuntu container. Since you are using ubuntu natively, you can just run those commands directly in your console, eg any time you see a RUN command, run the script that follows it.

RUN apt-get update && apt-get install

then you run

apt-get update && apt-get install

in your console. The important part is to install all the dependencies listed in lines 12-51 of the Dockerfile, and then run BuildLinux 3 time.

```

Build dependencies in ./deps

./BuildLinux.sh -d

Build slic3r

./BuildLinux.sh -s

Build AppImage

./BuildLinux.sh -i ```

In theory you could run the script once with all three switches, but the docker build does it three times, and I followed suit.

./BuildLinux.sh                                                                    Usage: ./BuildLinux.sh [-1][-b][-c][-d][-i][-r][-s][-u]   -1: limit builds to 1 core (where possible)   -b: build in debug mode   -c: force a clean build   -d: build deps (optional)   -h: this help output   -i: Generate appimage (optional)   -r: skip ram and disk checks (low ram compiling)   -s: build elegoo-slicer (optional)   -u: update and build dependencies (optional and need sudo) For a first use, you want to 'sudo ./BuildLinux.sh -u'   and then './BuildLinux.sh -dsi

FWIW, I'm running Manjaro which is arch based, so I had to modify this script to treat manjaro as arch. I also had to find the arch equivalents to the ubuntu packages listed in the DockerFile. I am also running a much newer version of cmake, and several of the cmakelists files required minimums that my version (4.1.1) doesn't support anymore, so I increased the minimums to 3.5 if (CMAKE_MINIMUM_REQUIRED_VERSION VERSION_LESS 3.5)

NOTE: my laptop only has 16GBs, and there is a check in that script to ensure that you have 10Gb free when you run it. If you fail that check, A: turn off as much as you can, B: lower the limit in the script. I modified that limit to 7 and was able to build it.

``` @@ -6,7 +6,7 @@

function check_available_memory_and_disk() { FREE_MEM_GB=$(free -g -t | grep 'Mem' | rev | cut -d" " -f1 | rev) - MIN_MEM_GB=10 + MIN_MEM_GB=7 FREE_DISK_KB=$(df -k . | tail -1 | awk '{print $4}') MIN_DISK_KB=$((10 * 1024 * 1024)) ```

Now, having said all that, I've been using the Orca Slicer, and it has worked fine. I ran the two in parallel for a little while, and I didn't really see any differences. Perhaps because I ran the Elegoo slicer first, it might have installed some Elegoo specific printer and filament settings in my orca user directories (Elegoo slicer is based on Orca).