From: Tobias H. <tob...@gm...> - 2012-10-12 13:30:24
|
Am 12.10.2012 14:29, schrieb Peter Wang: > On Fri, 12 Oct 2012 13:45:59 +0200, Tobias Hansen <tob...@gm...> wrote: >> Hi, >> >> I'm thinking about writing a MIDI addon for Allegro 5. Since my >> intention is to get it included into Allegro, I check with you first. >> >> I think it's a good choice to use libfluidsynth. The Allegro addon has >> to do the same things with libfluidsynth as Alure [1], so I intend to >> reuse some of Alures code. That means the addon would be partly under >> Alures license X11/MIT. There are free soundfonts available (I don't >> mean that Allegro must include one, but it's good to know). A reasonable >> one is [2] I think. It's GPL licensed. If you want to test >> libfluidsynth, you can use the alurestream program bundled with alure: >> >> FLUID_SOUNDFONT=<soundfont> alurestream <midifile> > > You might also want to look at the code I wrote: > > http://sourceforge.net/p/dunedynasty/dunedynasty/ci/f5a884821842ea9b414515f2742fccf4c45658a0/tree/src/audio/allegro_midi.cpp > > There's not much to it, honestly. > >> My questions are: >> >> 1. Is that something you would like to include into Allegro 5 if it >> works well? Do you see any problems with my plan? > > I'm thinking not, because fluidsynth is LGPL licensed. Allegro has has > traditionally shyed away from depending on GPL/LGPL licensed libraries > due to complications in distribution. > > Peter > Ok, thanks. Your allegro_midi.cpp is GPL licensed though. Would you put that file under LGPL or less restrictive? Best, Tobias |