Related to #1572
On older versions of macOS the current Cocoa backend cannot build. A typical solution in such cases is to use a Unix-style build, relying on X11/GTK, which work fine.
It is also workable here, however there a few complications:
-
The build does something exotic with icon files, converting them via binary command. I am not sure such a thing exists on macOS (and the code fails to compile on that part). Disabling that chunk in CMakeLists is trivial, but a few symbols from icon “library” are expected by the app, and stubbing out those disables some functionality, it seems.
-
Video functionality uses a Linux-specific library. On its own, it is used in a single file, however symbols from there are used in video-related functions. Just cutting it out should be straightforward, but maybe it can be implemented in a platform-independent way? There are a lot of apps which use X11/GTK and work fine on macOS without bringing in any non-portable stuff.
Related to #1572
On older versions of macOS the current Cocoa backend cannot build. A typical solution in such cases is to use a Unix-style build, relying on X11/GTK, which work fine.
It is also workable here, however there a few complications:
The build does something exotic with icon files, converting them via
binarycommand. I am not sure such a thing exists on macOS (and the code fails to compile on that part). Disabling that chunk in CMakeLists is trivial, but a few symbols fromicon“library” are expected by the app, and stubbing out those disables some functionality, it seems.Video functionality uses a Linux-specific library. On its own, it is used in a single file, however symbols from there are used in video-related functions. Just cutting it out should be straightforward, but maybe it can be implemented in a platform-independent way? There are a lot of apps which use X11/GTK and work fine on macOS without bringing in any non-portable stuff.