On Mon, Dec 8, 2008 at 2:43 PM, Michael Goffioul <[EMAIL PROTECTED]> wrote: > On Mon, Dec 8, 2008 at 1:06 PM, Jaroslav Hajek <[EMAIL PROTECTED]> wrote: >> On Mon, Dec 8, 2008 at 7:54 AM, Michael Goffioul >> <[EMAIL PROTECTED]> wrote: >>> Is MOSEK licensed under GPL? If not, how do you interface it with >>> octave? >>> >> >> Why not? There is no problem writing an interface to a proprietary >> library, provided that the interface itself will be GPL'ed. >> Writing such an interface certainly does not make the library a >> derivative work of Octave :) > > If the interface is an oct-file (hence linked against octave libraries), > then I think the interface, as well as the library, must be licensed > under GPL. We had the kind of discussion before, and I think that > GPLv3 is very explicit about this. Even distributing in source-form > only is not valid. >
The package must be GPLed, no question. The original library, certainly not. Or I must be missing something important. If my software A links to a library B and to Octave, the A is a derivative work of both B and of Octave, but certainly that does not make B a derivative work of Octave! If the license of B does not prohibit GPL-licensed derivative works, everything is OK. I think the situation is no different from, say, MinGW linking to Windows API. -- RNDr. Jaroslav Hajek computing expert Aeronautical Research and Test Institute (VZLU) Prague, Czech Republic url: www.highegg.matfyz.cz ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
