3 ms·
> ABI compatibility should not be a huge problem for distributions. That's just fine, until you want to release a binary application that targets more than one
by awalton 12y ago
> ABI compatibility should not be a huge problem for distributions.
That's just fine, until you want to release a binary application that targets more than one distribution...
- stefantalpalaru 12y agoIf you really want to do that you should statically link it.
- awalton 12y agoA wonderful idea. Let me just statically link an LGPL library into my Commercial application...
- catern 12y agoSure, just relicense your application under the GPL. You're getting these libraries for free. If you're not at all willing to contribute back, then you're obviously not the target audience.
- awalton 12y agoIf you check Gtk+'s history, I have contributed back on numerous occasions. Unfortunately, convincing the people who write my paychecks, VMware, to contribute Workstation and Player to the Open Source community seems to be a pretty big stretch.
- stefantalpalaru 12y ago"(1) If you statically link against an LGPL'd library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application." - http://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic http://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic So there you have it. Link statically against the LGPL library and package the object files of your commercial application.