| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
It's an issue for closed-source developers.
It's an issue for closed-source developers.
Posted Dec 31, 2003 5:15 UTC (Wed) by piman (subscriber, #8957)In reply to: It's an issue for closed-source developers. by arcticwolf
Parent article: LWN's Obviously Incorrect 2004 Predictions
These days, yes you do. Run ldd on your binary.
(Log in to post comments)
It's an issue for closed-source developers.
Posted Jan 5, 2004 19:38 UTC (Mon) by tbird20d (subscriber, #1901) [Link]
ldd links the application, then reports the linkages.The application is not linked until runtime (or until you run ldd),
which still begs the question of whether it is directly linked or not.
Linked, not linked - what's the difference ?
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.