diff options
| author | Mark Routledge <mark@mroutledge.co.uk> | 2022-08-04 01:51:47 +0300 |
|---|---|---|
| committer | supermerill <merill@free.fr> | 2022-08-11 00:57:17 +0300 |
| commit | 24fd7a4f79b24556debfcac37b684c69cf1b8547 (patch) | |
| tree | c6800f52fcf1d4fffe695e4b0169360823837b27 | |
| parent | b86a94ba549487af32c02daa980d97adfeb00dfb (diff) | |
Update How to build - Linux et al.md
Tips for updating on the RPI4.
| -rw-r--r-- | doc/How to build - Linux et al.md | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/How to build - Linux et al.md b/doc/How to build - Linux et al.md index 5b1726e96..d967edef3 100644 --- a/doc/How to build - Linux et al.md +++ b/doc/How to build - Linux et al.md @@ -173,6 +173,27 @@ May also be useful to run I'm sure there is some steps missing, please open an issue to let us know or open a pull request by editing this document. +To get this running / updated on an RPi running Raspberry Pi OS - Bullseye (64bit) you can run the ./BuildLinux.sh script, however it will not make the AppImage, but it will generate the application in the package folder that you can them move to somewhere convenient. + +e.g. navigate to clone repository + sudo ./BuildLinux.sh -s + sudo ./BuildLinux.sh -dsi + +It will fail, but (for me) ONLY when it tries making the AppImage. If you then copy the contents of the 'package' folder you should have a nice fully working instance. +**Note:** I think you can use `./BuildLinux.sh -ds` instead of `sudo ./BuildLinux.sh -dsi` and it should do the same thign without failing. I didn't tried. + +Move the package folder to a location of your choice e.g. + cp -R build/package /home/pi/SuperSlicer/ +Ensure the executable is runnable as default user pi. + cd /home/pi + sudo chown -R pi:pi SuperSlicer + Finally make the sure the program is executable +sudo chomod +x ~/SuperSlicer/superslicer + +Then run by calling +./home/pi/SuperSlicer/superslicer + + |