FreeFileSync Forum

I found a tutorial for FreeFileSync 10.22 on Github and updated it to FreeFileSync 10.25. Subere, 05 Jul 2020, 09:57

Excellent resource -- thank you!

Thanks for documenting the workaround.

Thanks much for the update. Hopefully we can get the current sources running on the Pi soon, and keep things working. The Pi 4 is a mighty little beast and would be a great platform for FFS.

Is it possible to get your binary executable? jper, 09 Nov 2019, 00:50

Sure. Message me jmsxl19307 at gmail dot com . Assuming I can find a drop zone that can handle ~90MB because you'll need the gcc shared libs too.

Suggestion: review the copy of the message to be a bit less aggressive and maybe program the filter to accept links to other threads on this forum Gabe, 21 Sep 2019, 11:03

Agree. The assumption of guilt is wrong. And if the post truly is spam, do I think the spammer will read (or care) about this warning? I think not.

Yes, please and for Mac OS too.

So, once you have all the build dependencies in place, FreeFileSync builds and runs correctly on the ARMv7 architecture?


Yes. I recently built FFS v10.14 on a Raspberry Pi 3B+ running Raspbian released July, 2019 based on Debian Buster.

No exhaustive testing, but an interactive mirror sync ...

Here's a web page that shows the steps to build on Linux: https://github.com/jeffli678/build-FreeFileSync

That page references another page https://solarianprogrammer.com/2016/10/07/building-gcc-ubuntu-linux/ that shows how to build a newer version of gcc, which you'll likely need to do as well ...

+1 on this idea. Would make reviewing the comparison results much easier.

It appears that you don't have dependency wxWidgets installed ("wx-config: not found")

A small quirk still present in v10.8. When two (or more?) configurations are run at the same time, the Last Sync values are not updated. When each config is run by itself Last Sync is updated. See attached screenshot of a just-completed backup. Prior backup was done about a week ago, yet after this ...

On Windows:
%APPDATA%\FreeFileSync\Logs
E.g.: C:\Users\<<user>>\AppData\Roaming\FreeFileSync\Logs

On MacOS:
~/Library/Application Support/FreeFileSync/Logs

Don't know about Linux.

I just want to say Thank You for continuing to work around the poorly implemented MTP. FFS's support of MTP is really good, in the face of such a botched protocol extension.

Check out viewtopic.php?t=5706#p18924

Starting with Mojave, macOS locks down a bunch of directories, including ~/Pictures (where Photos Library.photoslibrary resides)

Agree -- this really stings when it happens. IMO any operation that consumes a lot of time or resources shouldn't be dismissed without confirmation. Of course, "a lot" is subjective. As far as I'm concerned an option in GlobalSettings.xml to enable this protection would be fine too. Thanks for your ...

@HC1: Understood; thanks!

I got an unexpected result experimenting with FFS v9.0. With that version, the scanning operation progresses at a steady, nearly linear rate throughout the scan until it finishes. With v10.5 (and as I recall all 10.x and many 9.x versions,) the scanning jumps to ~80,000 files processed in the first ...

I have the same problem with a similar setup; Windows 10 and Macbook Pro each mirroring to a Synology NAS. Been this way since the 9.x releases. FFS on Windows 10 is blazingly fast; FFS on the Macbook runs in fits and starts. The first 82,000 files are searched in 2-3 seconds and then I get pauses ...

Ok, I think I got this solved. Starting in Mojave, need to grant apps permission to access parts of the filesystem.

(This post led me to the solution: https://github.com/hashicorp/vagrant/issues/10234 )

To do so, navigate to Apple -> System Preferences... -> Security & Privacy, select "Full Disk ...

Have the same problem; definitely the result of updating to Mojave. FreeFileSync version is unchanged; v10.4 used before (no problems) and after the OS update (problems.) Running FFS after the update, got a series of dialogs from Mac OS asking "Allow FreeFileSync access to you calendar?" / Contacts ...

+1 I agree, would be really nice to have a dark theme on macOS Mojave.