From dcbaf87048543e01289972a9df8b6e4ac669bf34 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Vojt=C4=9Bch=20Bubn=C3=ADk?=
 <5830947+bubnikv@users.noreply.github.com>
Date: Mon, 30 Aug 2021 14:32:05 +0200
Subject: [PATCH] Note on desktop integration (PrusaSlicer 2.4)

---
 doc/How to build - Linux et al.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/How to build - Linux et al.md b/doc/How to build - Linux et al.md
index cf47c9392..4a48147dc 100644
--- a/doc/How to build - Linux et al.md	
+++ b/doc/How to build - Linux et al.md	
@@ -87,3 +87,13 @@ If you instead want PrusaSlicer installed in a structure according to the File S
 This will make PrusaSlicer look for a fixed-location `share/slic3r-prusa3d` directory instead (note that the location becomes hardcoded).
 
 You can then use the `make install` target to install PrusaSlicer.
+
+### Desktop Integration (PrusaSlicer 2.4 and newer)
+
+If PrusaSlicer is to be distributed as an AppImage or a binary blob (.tar.gz and similar), then a desktop integration support is compiled in by default: PrusaSlicer will offer to integrate with desktop by manually copying the desktop file and application icon into user's desktop configuration. The built-in desktop integration is also handy on Crosstini (Linux on Chrome OS).
+
+If PrusaSlicer is compiled with `SLIC3R_FHS` enabled, then a desktop integration support will not be integrated. One may want to disable desktop integration by running
+    
+    cmake .. -DSLIC3R_DESKTOP_INTEGRATION=0
+    
+when building PrusaSlicer for flatpack or snap, where the desktop integration is performed by the installer.