We use code ported from other projects that use GPLv3. And that license requires all code used by new projects to be GPLv3 or newer.
SebanisuToday at 8:57 AM
if i leave the GPL v3 comment infront of a function is that enough to use the function in my code? or does my entire project need to be gpl v3?
quantumpencilToday at 9:02 AM
If you call the function by via either static/dynamic linking in your own code, that makes your entire project GPLv3 legally (not just that function). If you communicate with a running instance of a GPLv3 application via IPC or something but don't link (i.e, you have an output only dependency, no shared code/data structures between the projects) then your project isn't legally GPL3
SebanisuToday at 9:04 AM
So I need to change all my lisance.txt to gpl v3. i guess. and technically openviii is gpl v3 too because we have code ported from dieling. and all of dieling is gplv3.
quantumpencilToday at 9:05 AM
yep
NEW
[9:06 AM]
license is very infectious
We use code ported from other projects that use GPLv3. And that license requires all code used by new projects to be GPLv3 or newer.
SebanisuToday at 8:57 AM if i leave the GPL v3 comment infront of a function is that enough to use the function in my code? or does my entire project need to be gpl v3?
quantumpencilToday at 9:02 AM If you call the function by via either static/dynamic linking in your own code, that makes your entire project GPLv3 legally (not just that function). If you communicate with a running instance of a GPLv3 application via IPC or something but don't link (i.e, you have an output only dependency, no shared code/data structures between the projects) then your project isn't legally GPL3
SebanisuToday at 9:04 AM So I need to change all my lisance.txt to gpl v3. i guess. and technically openviii is gpl v3 too because we have code ported from dieling. and all of dieling is gplv3.
quantumpencilToday at 9:05 AM yep NEW [9:06 AM] license is very infectious