Timeline for License obligations when creating a statically linked executable
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2019 at 5:33 | comment | added | Bart van Ingen Schenau | @some_guy632: you could just add the mention of the ncurses library and its license text to the end of your manual. There is no need to have it as a separate file. | |
| Apr 11, 2019 at 5:12 | comment | added | some_guy632 | So right now I just have the executable. I don't have any documentation outside the game at this point. I intend to include a little manual and a "License" with the Unlicense text on it. If I'm reading this correctly I should include a second License text file with the ncurses license copied into it? | |
| Apr 10, 2019 at 15:19 | comment | added | amon |
yes but C compilers have the nasty habit of stripping license header comments from the binary. “If you are linking to a pre-built version …”, no, that library might not contain the notices either but instead put it into associated documentation files, such as /usr/share/doc/<name>/copyright. So in general, manual action is required in order for downstream software to use MIT-licensed statically linked libraries compliantly.
|
|
| Apr 10, 2019 at 14:47 | comment | added | Bart van Ingen Schenau | @amon: the MIT license requires that it is present in the software, but does not state how it must be present. It does not require that recipients of a binary can actually read the license. While it is good practice to mention all the licenses that apply to different parts in the GUI, I don't think that is an actual obligation where it comes to the MIT license. | |
| Apr 10, 2019 at 13:26 | comment | added | amon | Might be good to emphasize that MIT doesn't just forbid removal of notices, but requires that the notices are included in the software. Web browsers like Chrome/Firefox are a good example to emulate here. | |
| Apr 10, 2019 at 5:36 | vote | accept | some_guy632 | ||
| Apr 10, 2019 at 4:58 | comment | added | Brandin | Not in the title screen. In the documentation, or perhaps in an "about" screen of your application. | |
| Apr 10, 2019 at 4:27 | comment | added | some_guy632 | So something like "Made with the NCURSES library" in the title screen would suffice? | |
| Apr 9, 2019 at 17:23 | history | answered | Bart van Ingen Schenau | CC BY-SA 4.0 |