- User Since
- Apr 11 2016, 10:04 AM (183 w, 2 d)
Apr 14 2016
Here's the answer of the FSF :
Apr 11 2016
http://www.gnu.org/licenses/gpl-faq.en.html#WindowsRuntimeAndGPL is a recommandation of the FSF, it's a reference and a rule that must be followed if you use a GPL v2 or v3 license.
If you distribute a DLL into your software, it is then not considered as a system library and you must add its source code. That's impossible to add the source code of Microsoft DLL, so you can not include them in the installer.
I think you should ask to FSF, they are the best people to answer about this point.
Anyway, I think it's not a fair service to include DLL in the package because users don't know it. Any users prefer to know and control what is installed on their computer. So, an installer that tests if the same or a more recent version of VC++ is already installed and if not, downloads and installs it is the best choice. During the installation, the user has the choice of cancelling the installation. And after the installation, users can look at the list of installed programs and keep only the last version of the installed VC++. It's clean and transparent.
PHPServer, Shareaza with VC++ and other softwares with JAVA/Zulu/OpenJDK are making this correctly. Most of the professional proprietary softwares are making this too.
"You may not distribute these libraries in compiled DLL form with the program.
To prevent unscrupulous distributors from trying to use the System Library
exception as a loophole, the GPL says that libraries can only qualify as System
Libraries as long as they're not distributed with the program itself. If you
distribute the DLLs with the program, they won't be eligible for this exception
anymore; then the only way to comply with the GPL would be to provide their
source code, which you are unable to do."