Ray Donnelly <[email protected]> writes: >> Apart from that, libgcc*.dll comes with some hefty licensing issues. >> > > It makes no difference if you link statically or dynamically to > libgcc, from https://www.gnu.org/licenses/gcc-exception-faq.html > > .. 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."
>From the same FAQ: 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. Here libstdc++ is mentioned as an example. The same applies to every other library covered by the Runtime Exception. Is as if your application were partially infected by the GPL, as far as binary distribution goes. ------------------------------------------------------------------------------ _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
