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
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2021 at 7:24 | vote | accept | Piotr Grygorczuk | ||
| Feb 2, 2021 at 6:55 | answer | added | Bart van Ingen Schenau | timeline score: 1 | |
| Feb 1, 2021 at 21:31 | comment | added | Piotr Grygorczuk | The STL files are not part of my library. They are from GCC. There are two options. First option, user would need to download it from GCC repository and build himself/herself. Second opinion, for simplicity I could deliver those files together with my library. Still user would need to build all himself. In both cases all is delivered as source. I would like to release my library under MIT license. | |
| Feb 1, 2021 at 8:33 | comment | added | Bart van Ingen Schenau | When users build (an application using) your library, are those STL implementation files automatically included in the build, or do they need to take explicit steps to build those as well? What license is your library released under? | |
| Jan 31, 2021 at 13:27 | review | First posts | |||
| Feb 3, 2021 at 16:28 | |||||
| Jan 31, 2021 at 13:26 | history | asked | Piotr Grygorczuk | CC BY-SA 4.0 |