Timeline for Explicit linkage of GCC STL source code in end user's code - GPLv3 + GCC runtime exception
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2021 at 8:57 | comment | added | Bart van Ingen Schenau | @PiotrGrygorczuk, if you integrate those files in the build of your library, it can be argued that they have become part of your library. That would make your library a derivative work and requires that you license your library under the GPL with or without the linking exception. | |
| Feb 2, 2021 at 7:24 | vote | accept | Piotr Grygorczuk | ||
| Feb 2, 2021 at 7:23 | comment | added | Piotr Grygorczuk | Great answer! Just for clarification... "If those GCC files are not automatically built when someone builds your library and they are merely included [...]". Well, they are cc files and must be compiled at some stage by user as a separate library and linked all together. Does this make a difference? They are still independent work though. | |
| Feb 2, 2021 at 6:55 | history | answered | Bart van Ingen Schenau | CC BY-SA 4.0 |