Licensing

[Robotex]

Do I have the right using code::Blocks commercial to create proprietary software?

[MortenMacFly]

Do I have the right using code::Blocks commercial to create proprietary software?

As long as you don't use components of C::B itself in your own projects, then yes.

[Robotex]

As long as you don't use components of C::B itself in your own projects, then yes.

What do you mean about components? Source of C::B?

[MortenMacFly]

What do you mean about components? Source of C::B?

Yes. And even then there are exceptions where you CAN use the source code of C::B for proprietary software. OSS is of course completely out of the scope here.

To make is short: If you use C::B as your IDE ("only") than there is nothing you need to worry about.

[Robotex]

Ok, Thanks for help

[Mart]

I would like to ask a question about compilers and licenses, and since something very similar is discussed here, so I write in this thread.

Creation of proprietary software (as far as I understand it) should not be done with GNU GPL license compilers? By proprietary, I understand closed-source, so it cannot be done with GNU GPL tools, am I right?

However, use of other compilers that are not GPL, and are packaged in C::B can be used?

Is there any thread or webpabe discussing such compiler licensing issues? I was looking for something on internet for few hours now, and cannot find anything written in a concise way. I'm not good with this kind of stuff.
Thank you!  

[TDragon]

Creation of proprietary software (as far as I understand it) should not be done with GNU GPL license compilers? By proprietary, I understand closed-source, so it cannot be done with GNU GPL tools, am I right?

No, you are wrong. See <http://www.gnu.org/licenses/gpl-faq.html#CanIUseGPLToolsForNF>.

[oBFusCATed]

Creation of proprietary software (as far as I understand it) should not be done with GNU GPL license compilers? By proprietary, I understand closed-source, so it cannot be done with GNU GPL tools, am I right?

Wrong, GNU GPL covers only the source code of the tool, not the results produced by the tool. (see the link TDragon posted)
Also all libs that ship with GCC are GPL licensed, but there is a linking exception: you can link to gcc libs and the resulting binary is not a GPL licensed one, search the GCC site or the binary you've got for the exact license text.
I think glibc has the same exception in its license.

However, use of other compilers that are not GPL, and are packaged in C::B can be used?

Right, C::B can be used with VC++ and this one is quite not free (I know about the express edition, but this is not the same)...