Can I release a program under the GPL which I developed using non-free tools?
Which programs you used to edit the source code, or to compile it, or study it, or record it, usually makes no difference for issues concerning the licensing of that source code. However, if you link non-free libraries with the source code, that would be an issue you need to deal with. It does not preclude releasing the source code under the GPL, but if the libraries don’t fit under the “system library” exception, you should affix an explicit notice giving permission to link your program with them. The FSF can give you advice on doing this.
Which programs you used to edit the source code, or to compile it, or study it, or record it, usually makes no difference for issues concerning the licensing of that source code. However, if you link non-free libraries with the source code, that would be an issue you need to deal with. It does not preclude releasing the source code under the GPL, but if the libraries don’t fit under the “system library” exception, you should affix an explicit notice giving permission to link your program with them. Our FAQ about using GPL-incompatible libraries provides more information about how to do that.