It's an issue for closed-source developers.
It's an issue for closed-source developers.
Posted Dec 31, 2003 2:02 UTC (Wed) by arcticwolf (guest, #8341)In reply to: It's an issue for closed-source developers. by goonie
Parent article: LWN's Obviously Incorrect 2004 Predictions
Do I actually *directly* link to the Qt libraries when I build a KDE application, though?
Posted Dec 31, 2003 5:15 UTC (Wed)
by piman (guest, #8957)
[Link] (2 responses)
Posted Jan 5, 2004 19:38 UTC (Mon)
by tbird20d (subscriber, #1901)
[Link] (1 responses)
The application is not linked until runtime (or until you run ldd),
Posted Jan 8, 2004 22:04 UTC (Thu)
by khim (subscriber, #9252)
[Link]
Why the hell it's even discussed here ? It's not important if Qt is linked directly to application or not. It is important if it's derived work or not. And here answer is clear: you can not build kdelibs or KDE application wothout Qt, you program need deep understanding of Qt internals to work so it's clearly derived work. End of story. Is it linked or loaded via dlopen() it's irrelevant.
Posted Jan 8, 2004 3:19 UTC (Thu)
by elanthis (guest, #6227)
[Link]
These days, yes you do. Run ldd on your binary.
It's an issue for closed-source developers.
ldd links the application, then reports the linkages.It's an issue for closed-source developers.
which still begs the question of whether it is directly linked or not.
Linked, not linked - what's the difference ?
It doesn't matter if you directly link or not. If you link anything to the GPL, it becomes implicitly GPLd. If the LGPL library depends on the GPL library, it must be under the terms of the GPL. Therefor, any apps that link to the LGPL library are bound by the same terms as if they linked against the GPL library. At least, this is how it was explained to me by the FSF a few years ago when I had GPL vs BSD linking questions for them.
It's an issue for closed-source developers.