> On 26 Feb 2025, at 9:37 am, Mike wrote: > Jonas et al- > > OK. Probably against my better judgement, haha, I'm going to try to help. > > First off, these patches look good to me. They are necessary if we want to > try to support Windows. Plus Jonas figured out a couple of the errors I never > managed > to work out with Lightning and the VM. So I'm very impressed. > > A couple of questions... > > From what I can tell, these patches are from a cross-compilation toolchain. > Is that correct? > They won't build from source with a native MinGW toolchain because > of the DLL version number problem and a couple of other tweaks. > Do we care about making them build with a native toolchain? > > The DLL number version problem is that the native MinGW tools build DLLs with > a major version number: libfoo.so.3.2.1 => libfoo-3.dll > > If we do care about building with the native MinGW toolchain, > in my humble opinion, there isn't much value in supporting then many > versions of MinGW other than UCRT64.
Is there any doco on how to do that? > Does LilyPond care > about the old MinGWs? MINGW32? MINGW64? CLANG64? > Please say 'no'. Pretty please say 'no'. > > If you want to follow along as I noodle with this, my sandbox is > https://github.com/spk121/guile-jonas > I've spun up build actions for > - Ubuntu > - Ubuntu Distcheck > - Cygwin > - Cygwin Distcheck > - Msys > - MinGW > - MacOS > > Regards, > Mike Gran Cheers, Kim
