You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|**FuncHook**|[GPLv2 or later with a GPL linking exception](https://github.com/kubo/funchook/blob/master/LICENSE)|
88
+
89
+
## 4. Ports
90
+
91
+
### 4.1 Swig
92
+
93
+
| Software | License |
94
+
| :------: | :-----: |
95
+
|**SWIG**|**∅**|
96
+
97
+
>When SWIG is used as it is distributed by the SWIG developers, its output is not governed by SWIG's license (including the GPL). SWIG's output contains code from three sources:
98
+
>
99
+
> - code generated by SWIG, which is not governed by copyright;
100
+
> - code copied from the SWIG library which is permissively licensed to be redistributed without restriction;
101
+
> - code derived from the user's input, which may be governed by the license of the code supplied by the user.
102
+
>
103
+
>So, while the input supplied to SWIG may affect the license of SWIG's output (e.g. if the input code is licensed under a copyleft or proprietary license), SWIG's license does not affect the license of the output. This is consistent with the FSF's FAQ entries on this subject ([GPLOutput](http://www.gnu.org/licenses/gpl-faq.html#GPLOutput) and [WhatCaseIsOutputGPL](http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL)), because the SWIG code copied into the output by SWIG is not GPL-licensed.
0 commit comments