Olivier Dion writes:
Hi Olivier,
> For example, I see a lot of patches for Windows recently, but I have
> never used Guile myself on Windows. I need to know more about this
> topic to help better.
Han-Wen and I created a MinGW cross-build in the 1.8 era to allow
creating LilyPond binaries for Windows without having access to such a
system (sadly, many musicians were/are(?) were stuck with Windows), but
every major release that would break. That's the reason for submitting
a recipe to check the current MinGW cross-build with Guix:
https://codeberg.org/guile/guile/pulls/90
We've had long-standing mingw branches that mostly Mike Gran and I would
work on, now and then, e.g.,
https://codeberg.org/janneke/guile/commits/branch/wip-mingw-guile-2.2
Almost excatly five years ago, I created a 64-bit port
https://codeberg.org/janneke/guile/commits/branch/wip-mingw-3.0.8
on top of Mike's recent work with help from him and Andy, but it had an
awfully large patch
https://codeberg.org/janneke/guile/commit/91d27b579f58b8aa214912fd7324747b248b0ad4
and never got merged. So we've just been patching Guile ourselves (to
create Windows binaries for Dezyne, for example). Recently, Jonas
Hahnfeld managed to split that patch up in several bits, make fixes for
lightening, and get it merged; lovely!
We're still carrying a number of patches, e.g., on
https://codeberg.org/spk121/guile/commits/branch/wip-mingw-2026
and
https://codeberg.org/janneke/guile/commits/branch/wip-mingw-2026
some of which (compile time file-name-convention for MinGW) are too
broken and ugly to merge and for which there's no solution yet.
> But first, I need to know if this interest someone! I was thinking to
> make a online meeting (e.g. Jitsi) every 3 months (to begin with). Any
> questions and discussions about Guile are welcomed!
Good idea!
Greetings,
Janneke
--
Janneke Nieuwenhuizen <[email protected]> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
