On Mon, 2025-08-25 at 21:03 +0200, Dr. Arne Babenhauserheide wrote:
> Liliypond just had a release again, and it would be great if we could
> get Guile to a point that Lilypond does not have to patch it anymore for
> their Windows-releases.

We're patching since a long time, but yes it would be great if there
was an upstream release that "just worked" (tm) on 64-bit Windows.

> I had high hopes in May that we could get there quickly, but time has
> flown by again
> 
> Would it be OK for you if I merged the Lilypond patches and you’d rebase
> your patches on top of theirs?
> 
> Are there any regressions caused by the Lilypond patches?

The refactoring patches should be relatively safe and, as far as I can
remember, the actual changes only take effect if sizeof(long) <
sizeof(void *), which is effectively only the case for 64-bit Windows.

Jonas

Attachment: signature.asc
Description: This is a digitally signed message part

  • Re: Guile 64-bit ... Maxime Devos
    • Re: Guile 64... Mike Gran
      • Re: Guil... Maxime Devos
        • Re: ... Mike Gran
          • ... Dr. Arne Babenhauserheide
            • ... Dr. Arne Babenhauserheide
              • ... Developers list for Guile, the GNU extensibility library
              • ... Dr. Arne Babenhauserheide
              • ... Dr. Arne Babenhauserheide
              • ... Developers list for Guile, the GNU extensibility library
  • Re: Guile 64-bit ... Developers list for Guile, the GNU extensibility library
    • Re: Guile 64... Developers list for Guile, the GNU extensibility library
      • Re: Guil... Dr. Arne Babenhauserheide
      • Re: Guil... Developers list for Guile, the GNU extensibility library
        • Re: ... Dr. Arne Babenhauserheide
        • Re: ... Thompson, David
          • ... Developers list for Guile, the GNU extensibility library
            • ... Thompson, David
              • ... Developers list for Guile, the GNU extensibility library
              • ... Developers list for Guile, the GNU extensibility library

Reply via email to