Hacker News new | ask | show | jobs
by spc476 5532 days ago
It does allow static linking---from section 4, paragraph d:

"d) Do one of the following:

"0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.

"1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version."

You just have to allow relinking in some form. Admittedly, this is easier with dynamic linking, but the LGPL doesn't restrict static linking per se.

1 comments

Yes. It's like saying humans can fly, if thrown out of an airplane. Asking developers to distribute all the object files of their proprietary software is not realistic. And even if one developer accepts that condition, most developers won't, sending any open source software that she releases and that depends on an LGPL library directly into oblivion (again, in a context where dynamic linking is not possible).