Both are allowed. You should pay particular attention to section 6 of LGPL 2.1. You have to allow private modification and reverse engineering for your closed source app. You probably want option 6b, which in your case just means users can install modified QT DLLs. IANAL.
1) is can I legally bundle the QT *.dll files in my installer?
This is the recommended solution - it allows the user to upgrade to later versions of Qt easily.
2) can I legally bundle my final *.EXE files even if it's compilation/linkage depends on QT *.LIB files
Do you mean you use the Qt stub .libs to build a dll version or are you statically linking an exe ( no Qt DLLs required)? It must be possible to relink Qt. If you are statically linking Qt this probably means you have to make object or raw library versions of your app available (depends on your OS)
发布评论
评论（2）
两者都是允许的。您应特别注意 LGPL 2.1 的第 6 节。您必须允许对您的闭源应用程序进行私人修改和逆向工程。您可能需要选项 6b，在您的情况下，这仅意味着用户可以安装修改后的 QT DLL。 IANAL。
Both are allowed. You should pay particular attention to section 6 of LGPL 2.1. You have to allow private modification and reverse engineering for your closed source app. You probably want option 6b, which in your case just means users can install modified QT DLLs. IANAL.
这是推荐的解决方案 - 它允许用户轻松升级到更高版本的 Qt。
您的意思是使用 Qt 存根 .libs 来构建 dll 版本还是静态链接 exe（不需要 Qt DLL）？
必须可以重新链接 Qt。如果您静态链接 Qt，这可能意味着您必须使应用程序的对象或原始库版本可用（取决于您的操作系统）
This is the recommended solution - it allows the user to upgrade to later versions of Qt easily.
Do you mean you use the Qt stub .libs to build a dll version or are you statically linking an exe ( no Qt DLLs required)?
It must be possible to relink Qt. If you are statically linking Qt this probably means you have to make object or raw library versions of your app available (depends on your OS)