Quoting Antoine Schmitt <[email protected]>:
Le 26 août 09 à 21:03, [email protected] a écrit :
As for Windows, there have been contributions from many
individuals, but I don't think we have ever officially knighted a
Windows maintainer. Antoine Schmitt? Pedro Lopez-Cabanillas?
Hi all,
I'm following all these threads, but unfortunately, I don't have much
time on my hands to work on fluidsynth these days.
I had indeed more or less maintained an old version of fluidsynth on
the Windows platform, but I don't even have VisualC++ installed on my
new PC these days, so I don't think that I can be the Windows knight...
Something that's more on my todo list is the iPhone port. I hope to be
able to look into this one of these coming weeks. But again, no
promises. So no knighting.
How about the "Duke" of Windows and/or iPhone then? ;)
About the fluidsynth on iPhone, indeed dynamic libraries are
impossible, but direct linking of libraries is possible AFAIK. So would
that also make the resulting app LGPL ? I don't think so...
LGPL allows public distribution of commercial applications dynamically
linked to an LGPL library. Static linking on the other hand, is
considered a "derivative work", when publicly distributed, and thus
the application would have to be licensed compatibly. Unfortunate for
systems without dynamic linking, when trying to create a commercial
product. The idea behind the GPL and LGPL is to try to prevent
commercial abuse of software, in which a company attempts to prevent
public access to the software, by creating derivatives and restricting
users rights to it. Static linking would be an easy way to subvert
this protection, but I agree that the lines get blurry when comparing
between static and dynamic linking.
I personally like the BSD license for certain things, since it allows
for easy use in embedded environments and is less restrictive (more
"free" in my opinion). It would be pretty difficult to change the
license of FluidSynth though, since it would require consulting those
in AUTHORS to get their permission.
At any rate, I don't mean to start some sort of license thread.. They
can get pretty tiresome ;)
Apart from this, have no other clues, either about glib or fluidsynth.
I'll keep you update as soon as I put my nose into this more deeply.
Cheers !
++ as
Cheers.
Josh
_______________________________________________
fluid-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/fluid-dev
