This forum has been archived. All content is frozen. Please use KDE Discuss instead.

LGPL and closed source

Tags: None
(comma "," separated)
bomboze
Registered Member
Posts
12
Karma
0

LGPL and closed source

Mon Jun 22, 2009 9:30 am
I've read here that Eigen has closed source users thanks to LGPL library. But how is it possible to compile Eigen as a shared library (which LGPL requires you to do if you close your sources)?

The problem is that Eigen doesn't really have .c/.cpp which would be compiled into shared library, since all of the code is in .h files. Am I missing something here?
Seb
Registered Member
Posts
99
Karma
0

RE: LGPL and closed source

Mon Jun 22, 2009 9:48 am
Yes, you refer to LGPLv2/v2.1
Eigen is distributed under version 3.

If using v2.1, a header-only library would be equivalent to GPL. With v3 you can write proprietary software using a header only lib.
bomboze
Registered Member
Posts
12
Karma
0

RE: LGPL and closed source

Mon Jun 22, 2009 10:05 am
Seb wrote:If using v2.1, a header-only library would be equivalent to GPL. With v3 you can write proprietary software using a header only lib.


Thanks for the explanation, Seb!

So, Basically if a library contains only .h files LGPL 3 allows you to compile it into your final executable statically. Did I get that right?

Wow, kudos to Eigen for this! :)
User avatar
bjacob
Registered Member
Posts
658
Karma
3

RE: LGPL and closed source

Mon Jun 22, 2009 11:28 am
Eigen is a pure template lib (only headers), there used to be a problem with this in the LGPL 2.1, that's why we specifically require LGPL3+ which fixes this issue, see
http://eigen.tuxfamily.org/index.php?ti ... #Licensing

Last edited by bjacob on Mon Jun 22, 2009 11:31 am, edited 1 time in total.


Join us on Eigen's IRC channel: #eigen on irc.freenode.net
Have a serious interest in Eigen? Then join the mailing list!


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot]