Justin Seyster <jrs...@gmail.com> writes:
> Thanks for this advice. The link to the GCC Exception was especially helpful.
>
> The trick here is that I'm actually releasing a library designed to be
> linked into plug-ins. I want the library itself to be copyleft but
> for plug-in authors to retain any licensing flexibility that they
> would have when releasing a stand-alone GCC plug-in.
>
> It sounds like the GPLv3 will do that for me, so that's my plan unless
> somebody corrects me.
I would recommend using the GPLv3 with an explicit reference to the GCC
Runtime Library Exception, as in:
XXX is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3, or (at your option)
any later version.
XXX is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
Under Section 7 of GPL version 3, you are granted additional
permissions described in the GCC Runtime Library Exception, version
3.1, as published by the Free Software Foundation.
You should have received a copy of the GNU General Public License and
a copy of the GCC Runtime Library Exception along with this program;
see the files COPYING3 and COPYING.RUNTIME respectively. If not, see
<http://www.gnu.org/licenses/>.
Ian
