Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: noname| on July 19, 2007, 02:36:35 pm
-
hi,
I have a question.
What licenses could I choose for my developed software?
I write primary freeware, but most of them are not open-source now.
If it is possible i do not want to use the GPL or LGPL.
I would be more happy with a license which for example HydraIRC uses (or closed-source)
thanks
NoName|
-
http://en.wikipedia.org/wiki/Software_license (http://en.wikipedia.org/wiki/Software_license)
http://en.wikipedia.org/wiki/Comparison_of_free_software_licences (http://en.wikipedia.org/wiki/Comparison_of_free_software_licences)
http://en.wikipedia.org/wiki/Open-source_license (http://en.wikipedia.org/wiki/Open-source_license)
http://www.gnu.org/philosophy/license-list.html (http://www.gnu.org/philosophy/license-list.html)
It's up to you to decide.
-
Yes perhaps I doesn't choose the right words.
I want to develop with codeblocks and my question is, if it is up to me to choose the license or whether there are restrictions by the GPL license under which is CodeBlocks released?
Sorry, I thought it would be clear that CodeBlocks is used ;)
NoName|
PS: Anyway, thanks for the answer...
-
There shouldn't be any restrictions as long as you aren't using parts of codeblocks sourcecode in your projects.
Anyway there may be some restrictions from the compiler you are using.
-
I want to develop with codeblocks and my question is, if it is up to me to choose the license or whether there are restrictions by the GPL license under which is CodeBlocks released?
Stand-alone software you develop using C::B can be any license. Hence if you use (parts of) C::B (e.g. C::B's SDK) it's becoming different. So let's say you develop a cool closed-source C::B plugin and distribute C::B with this plugin without source. That would be bad. But as soon as you talk about developing stand-alone software and you use the C::B IDE as binary for that purpose (and not the source of C::B) which I suppose you are about to do you can freely choose any license for your app.
With regards, Morten.
-
Thanks ;)
The compiler I used is MinGW at the moment, but I read that there is in opposite to the Cygwin/GCC no restriction in that way.
If i'm wrong please correct me
NoName|
-
why the GPL aversion?
-
Thanks ;)
The compiler I used is MinGW at the moment, but I read that there is in opposite to the Cygwin/GCC no restriction in that way.
If i'm wrong please correct me
NoName|
MinGW - Licensing Terms
MinGW base runtime package is uncopyrighted and placed in the public domain. This basically means that you can do what you want with the code.
w32api
You are free to use, modify and copy this package. No restrictions are imposed on programs or object files compiled with this library. You may not restrict the the usage of this library. You may distribute this library as part of another package or as a modified package if and only if you do not restrict the usage of the portions consisting of this (optionally modified) library. If distributed as a modified package then this file must be included.
The Cygwin API library found in the winsup subdirectory of the source code is also covered by the GNU GPL (with exceptions; see below). By default, all executables link against this library (and in the process include GPL'd Cygwin glue code). This means that unless you modify the tools so that compiled executables do not make use of the Cygwin library, your compiled programs will also have to be free software distributed under the GPL with source code available to all.
I think that with Mingw you can create commercial programs but not with Cygwin