Trying to make FreeFileSync easier to build (GitHub repo inside)

[ccssne]

I've recently started a project to simplify the process of building FreeFileSync from source — especially to make it possible to compile directly via GitHub Actions.

You can find my current fork code here:
👉 https://github.com/dddu809-max/FreeFileSync-easybuild/

Right now, I’m running into quite a few build difficulties, so if anyone has experience or ideas about automating the build process, or if you just want to join in and explore the setup together, that would be fantastic.

The goal is to have a fully open and reproducible workflow for compiling FreeFileSync, ideally without manual setup pain.

Any contributions, hints, or feedback are very welcome!

Thanks in advance,
ccssne

[ccssne]

[ccssne]

First, I developed the freefilesync that could only run on the ubantu-2404 version. Then, I continued to modify the code to make it compatible with the 2204 version. Although there are still some minor issues at present, the system has been successfully built and is now running. The Windows version is still unclear at the moment. Does anyone have any ideas on how to compile it?

[bgstack15]

I build with this dpkg build recipe: https://gitlab.com/bgstack15/stackrpms/-/tree/master/freefilesync?ref_type=heads

I use Open Build Service: https://build.opensuse.org/package/show/home:bgstack15/freefilesync, which pulls from that gitlab location and a custom git repository that tracks upstream releases directly.

[ccssne]

@bgstack15 Thanks for the reply! Your setup looks way more professional than mine. I’m just a beginner, so I really appreciate you sharing your method — learned a lot from it!

I build with this dpkg build recipe: https://gitlab.com/bgstack15/stackrpms/-/tree/master/freefilesync?ref_type=heads

I use Open Build Service: https://build.opensuse.org/package/show/home:bgstack15/freefilesync, which pulls from that gitlab location and a custom git repository that tracks upstream releases directly.