our internal JIT compiler kaba needs to adapt to a different ABI
I don't understand visual studio and the build system well enough
gtk
Yes, there are multiple ways of using gtk on windows. Sadly, they seem to get abandoned fairly quickly. I had my hopes on vcpkg but since gtk4 it is only usable with heavy workarounds.
I still need to check out how to bundle everything. At least theming has gotten easier since gtk4.
kaba
There was a major bug in the calling convention that I've fixed recently. And I'm carefully optimistic after a couple of experiments. Needs more proper testing before I'll call it stable.
build system
As much as I dislike cmake, it is the only realistic and """reliable""" system. I'm automatically generating cmake files with a script from a list of required and optional libraries.
Visual studio can handle cmake files. It seems to require some additional files that my script has (partially) learned to generate.
Libraries on windows are still a nightmare though. From what I've tried, vcpkg still seems like the best option. Yes, some libraries are screwed up, but most work. And cmake integration is finally supported out-of-the-box.
Outlook
I finally got the program running again yesterday. What is missing:
more testing
automatic ci builds? (not sure if that is possible with the current way of using gtk)
smaller fixes in the build system
enabling support for ogg and flac files again
some musical unicode symbols are not supported
native backend? (at least pick better devices in portaudio)
The biggest blockers here are:
gtklibrary is not well supported on windowsgtk
Yes, there are multiple ways of using
gtkon windows. Sadly, they seem to get abandoned fairly quickly. I had my hopes onvcpkgbut sincegtk4it is only usable with heavy workarounds.Currently I got it working using https://github.com/wingtk/gvsbuild but who knows.
I still need to check out how to bundle everything. At least theming has gotten easier since
gtk4.kaba
There was a major bug in the calling convention that I've fixed recently. And I'm carefully optimistic after a couple of experiments. Needs more proper testing before I'll call it stable.
build system
As much as I dislike
cmake, it is the only realistic and """reliable""" system. I'm automatically generatingcmakefiles with a script from a list of required and optional libraries.Visual studio can handle
cmakefiles. It seems to require some additional files that my script has (partially) learned to generate.Libraries on windows are still a nightmare though. From what I've tried,
vcpkgstill seems like the best option. Yes, some libraries are screwed up, but most work. Andcmakeintegration is finally supported out-of-the-box.Outlook
I finally got the program running again yesterday. What is missing:
gtk)portaudio)