c++ - How to allow private modifications when using Qt in a commercial product under the LGPL -


i'm considering building closed-source application dynamically links against qt libraries. target platforms linux , windows. in order fulfill obligations of lgpl:

"the user of application has able re-link application against different or modified version of qt library" (qt faq).

i'm struggling understand technically necessary make possible. without releasing source code.

  1. under conditions user able replace .so/.dll files ship application own, modified versions?

  2. is possible @ all? because on same matter libstdc++ faq states:

    the lgpl requires users able replace lgpl code modified version; trivial if library in question c shared library. there's no way make work c++, of library consists of inline functions , templates, expanded inside code uses library. allow people replace library code, using library have distribute own source, rendering lgpl equivalent gpl.

thank you!

edit: second issue clarified lgpl version 3, section 3. useful reference: old version of eigen faq discussing issue , correspondence fsf it.

in practice, people linking shared library qt; upgrading qt -as long common api remains, possible. advanced user in principle adapt qt library (starting source code of version using) fit needs (e.g. correct naughty bug, in particular without touching qt header file). of course give details him (at least, mention version of qt linking against).

in principle, noticed, might perhaps not enough. trial , judge decide, ask lawyer.

of course not lawyer.

btw, did consider asking manager or client (or legally responsible person) release code free software , publish (e.g. under gplv3+ on github)? in biased opinion, best solution!


Comments

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

linux - disk space limitation when creating war file -