On Fri, Oct 26, 2012 at 8:05 AM, Ruben Van Boxem <[email protected]> wrote: > 2012/10/26 Earnie Boyd <[email protected]> >> >> On Thu, Oct 25, 2012 at 9:07 PM, JonY wrote: >> > Microsoft DLLs when possible, eg msvcrt.dll, though it is not possible >> > unless you stick strictly to C. Like Kai says, C++ support comes from >> > GCC libstdc++, fortran support from libgfortran etc. You should have no >> > legal problems distributing these DLLs with your programs in anyway. >> >> As long as the source of those DLL libraries is also distributed. >> Distributing binaries of GPL code (LGPL is GPL with an exception for >> binary use) requires you to also distribute the source for those >> binaries; there is never an exception for that. > > > IANAL, but I can read. > > Stop spreading FUD. The GCC runtime libraries fall under a special exception > which is very liberal, as JonY intended to make unambiguously clear. Read up > on the subject here. The FAQ clearly states you can create proprietary > programs with these libraries as long as you don't use a non-GPL compatible > GCC plugin to do code generation. It even explicitly states that you can > combine code generated by the Intel compiler with GCC-generated code, and > still be able to use the exception to just redistribute the runtime > libraries alongside your binaries. This has nothing to do with the license > of the code actually being compiled and linked.
IANAL either but I am not spreading FUD. The exception covers the use and not the distribution. If you don't believe me ask Richard Stallman. <quote site="http://www.gnu.org/licenses/gcc-exception-3.1-faq.html";> I use a proprietary compiler toolchain without any parts of GCC to compile my program, and link it with libstdc++. My program itself does not include any runtime library code the same way that GCC-compiled programs include libgcc. Can I still take advantage of the exception? Yes. While combining libgcc with GCC-compiled object code is probably the most common way the exception is used, neither the GPL nor the GCC Runtime Library Exception distinguish between static linking, dynamic linking, and other methods for combining code in their conditions. The same permissions are available to you, under the same terms, no matter which method you use. Note that if you distribute libstdc++ as an independent library, you will need to follow the terms of the GPL when doing so. For example, if you distribute the library itself in object code form, you will need to provide source code to your recipients using one of the methods listed in section 6 of GPLv3. But as long as you are eligible to take advantage of the GCC Runtime Library Exception's permissions for your own program, the GPL's terms do not extend to it. </quote> -- Earnie -- https://sites.google.com/site/earnieboyd ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
