Federico Bruni <f...@inventati.org> writes: > Il giorno mer 20 lug 2016 alle 17:51, Mojca Miklavec > <mojca.miklavec.li...@gmail.com> ha scritto: >> I tried to compile lilypond (2.19.44) from source. And the midi file >> generate with that binary seems OK. >> >> (I'm even more happy that the binary didn't actually crash because >> it's compiled against a different stdlib than its dependencies.) >> >> Is it possible that the problem with the official binary is only there >> because I'm using a 32-bit binary on a 64-bit system? > > Maybe this issue explains it? > https://sourceforge.net/p/testlilyissues/issues/2208/
Frankly, midi.c is the only Python/C module we have _and_ the only C source code in the project and it appears to do a fairly simple job. The crossplatform/build/run trouble we are having with it does not seem commensurate to me with the functionality it provides. It does not appear what it does it all that complicate. Maybe we should aim to replace it with Python code and/or rewrite midi2ly to reuse some standard library? Python is the world of libraries, isn't it? -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
