Can I use GPL-covered editors to develop non-free programs? Can I use GPL-covered tools to compile them?
Yes, because the copyright on the editors and tools does not cover the code you write.
Some programs copy parts of themselves into the output for technical reasons--for example, Bison copies a standard parser program into its output file. In such cases, the copied text in the output is covered by the same license that covers it in the source code. Meanwhile, the part of the output which is derived from the program's input inherits the copyright status of the input.
As it happens, Bison can also be used to develop non-free programs. This is because we decided to explicitly permit the use of the Bison standard parser program in Bison output files without restriction. We made the decision because there were other tools comparable to Bison which already permitted use for non-free programs.
The only point where I think this may applies is when you sell your source. Part of you source contains macros copied in by Classbuilder, but based on the above only the macros are covered by the GNU GPL license and not your part of the source. As for the executable for your application, the macros would be compiled out and therefore any reference to Classbuilder generated code would be gone. I am not a Lawyer but this is how I understand it.
Craig Gunhouse
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a question about the GNU GPL of Classbuilder. Can the generated code, as generated by Classbuilder, be used without the GNU/GPL rules?
With other words: if I use Classbuilder in a project to create C++ files, am I obliged to make that project, or the created C++ files, also public?
If that would be the case, the tool cannot be used in the company I work for
Good question, maybe this will help.
From: http://www.gnu.org/licenses/gpl-faq.html#CanIUseGPLToolsForNF
Can I use GPL-covered editors to develop non-free programs? Can I use GPL-covered tools to compile them?
Yes, because the copyright on the editors and tools does not cover the code you write.
Some programs copy parts of themselves into the output for technical reasons--for example, Bison copies a standard parser program into its output file. In such cases, the copied text in the output is covered by the same license that covers it in the source code. Meanwhile, the part of the output which is derived from the program's input inherits the copyright status of the input.
As it happens, Bison can also be used to develop non-free programs. This is because we decided to explicitly permit the use of the Bison standard parser program in Bison output files without restriction. We made the decision because there were other tools comparable to Bison which already permitted use for non-free programs.
The only point where I think this may applies is when you sell your source. Part of you source contains macros copied in by Classbuilder, but based on the above only the macros are covered by the GNU GPL license and not your part of the source. As for the executable for your application, the macros would be compiled out and therefore any reference to Classbuilder generated code would be gone. I am not a Lawyer but this is how I understand it.
Craig Gunhouse