userspace) tools that will mount the mtp device like it is a regular filesystem. One way to do this for MTP-connected devices is to use any of the various FUSE (Filesystem in USErspace don't get bogged down in kernel space vs. So what you want to do is find a way to mount the mtp device (i.e., your phone) so that it is treated as a regular filesystem that any program will be able to use. The protocol "mtp://" would be a good indicator that Dolphin is using its advanced functionality that is not extensible to other programs such as FreeFileSync. These are neat features, but if the right libraries are not installed, and you do not mount the device/location as a filesystem on the kernel level, then other programs cannot access those items the same way.īy your coming here for help, I surmise that the location string in Dolphin was not merely a "/run/user/1000/android-29839183487" and instead was something like "mtp:///android-23828472/Internal Storage/". They could either use the low-level libraries like libsmb themselves or actually bundle the functionality into the file manager directly. 2.File managers like Dolphin (which is part of the whole KDE suite) tend to include advanced functionality like the abilities to view SMB (Samba: i.e., Windows network shares) or MTP (mobile devices) among other things.
Now the zip file should contain all the dependencies and the binary Bin/FreeFileSync_armv7l is able to run on a new raspberry pi assuming the target is running a current verions of Raspbian. Note the build needs about 8 GB of free disk space and takes about 4 hours on the Raspberry Pi 4 (4 GB), over 6 hours on the Raspberry Pi 3B+ and over 50 hours on the Raspberry Pi Zero.
Before running, be sure to review and update the config in build_gcc.sh according to your device (default is Raspberry Pi 4). See build_gcc.sh for the script with only C/C++ languages enabled.
As such, if you want to compile FreeFileSync on Raspberry Pi OS, you'll need a fresh version of gcc (the default version of gcc with RaspberyPi OS will not have all the necessary support).įor FFS v11.23, you'll need at least gcc 12.1.0įollow the instruction at: to build and install the gcc 12.1.0 with minor modifications. 3.1 gcc w/ good C++20 supportįreeFileSync requires good support of the C++20 standard and often takes advantage of the latest refinements once available across the major compilers (see for some background). The following dependencies could not be installed via apt-get and need to be compiled from their source code. Compile dependencies not available via apt-get
The following dependencies need to be installed to make the code compile.ģ. This may lead to a non-optimal user experience- see:
These instructions reflect building FreeFileSync using libgtk-3. Install available dependencies via apt-get zip file to the desired directory and uncompress Simply try the wget command a second time or you can manually download it through a browser. Download and extract the FreeFilesSync source codeĪs of this writing, the latest version of FreeFileSync is 11.23 and it can be downloaded from:įor some reason, wget DID NOT successfuly download the file on the first try (instead it downloads a portion and silently exits). This version of instruction apply to the following: Itemġ. These instruction capture the necessary steps for installing the necessary dependencies and compiling FreeFileSync on 32-bit Raspberry Pi OS (formerly referred to as Raspbian) FreeFileSync is a great open source file synchronization tool.īuilding from source on linux is straightfoward if all the necessary dependencies are installed.