Author Topic: Understanding the license, GPL  (Read 2858 times)

GNG

  • Guest
Understanding the license, GPL
« on: February 28, 2016, 01:47:51 pm »
Quote
Quote
"Code::Blocks is distributed under the GPL v3.0 license ...

The only exception is the SDK which is allowed to be linked by closed-source plugins."

I don't think you understand the GPL at all. No offense.  Please explain, using logic, how this is GPL safe.  The whole point of the GPL is precisely to limit you from doing this exact act. As the author of GNG is Not GNU I should know. I plan to add a section to the site which publicizes projects violating the GPL which I've found hundreds of without even looking hard.

Sounds to me like you were aiming for a L-GPL license, which even that is too restrictive to do many things and people often use a modified LGPL instead, which is more permissive.

I won't comment on the text that says "anyone can use it freely" which is pure falsehood.
« Last Edit: February 28, 2016, 01:51:09 pm by GNG »

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5247
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Understanding the license, GPL
« Reply #1 on: February 28, 2016, 02:32:03 pm »
Quote
Please explain, using logic, how this is GPL safe.  The whole point of the GPL is precisely to limit you from doing this exact act.
I'm not a lawyer, so this is from my personal point.
1, if you change the CB's source, and try to redistribute CB, then you should also supply the modified CB's source.
2, if you create a private plugin which only dynamically link the CB's sdk shared library, then you are not allowed to supply your plugin's source.

I'm not sure it violate C::B license.

Do you mean this(the above two cases) is exactly the same as LGPLv3?
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12121
    • Travis build status
Re: Understanding the license, GPL
« Reply #2 on: February 28, 2016, 05:51:20 pm »
@GNG: What is the purpose of this topic? What are you trying to achieve?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Re: Understanding the license, GPL
« Reply #3 on: February 28, 2016, 08:20:23 pm »
@GNG: What is the purpose of this topic? What are you trying to achieve?
That's not really important.
Fact is, the license text on our website is incorrect.
And the sdk is not GPLv3 but LGPLv3 as far as I know.

Nevertheless, we should overwork (at least) this site.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12121
    • Travis build status
Re: Understanding the license, GPL
« Reply #4 on: February 28, 2016, 11:23:11 pm »
That's not really important.
It is important, because he is reporting some problem, but he doesn't clearly state what the problem is. We have to guess what it is.
Obviously you've read his mind and you've guessed the problem, but why should it be hard, when it could be easy and clear?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: Understanding the license, GPL
« Reply #5 on: February 29, 2016, 10:26:59 am »
Changed that accordingly, see here:

http://codeblocks.org/license

For clarification: C::B is GPLv3, SDK is LGPLv3.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ