GNU GCC Questions

GNU GCC Questions

[Source Code]

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

Hello dear GNU GCC team! I would like to ask you some questions:
1. Is GNU GCC completely free software? Can I use it for commercial and
non-commercial projects without opening the source code?
2. Can I use GNU GCC on windows, linux and macOS? And at the same time not
to use additional software, for example: Visual Studio?
3. Under what circumstances should I make my projects open source?
4. Can I use any headers in my projects? Or I should my projects open
source?

P.S. I really like your GNU GCC product and would really like to use it for
C/C++ practice, maybe use it for commercial products in the future. But I
really don't want to make my projects open source :)

Re: GNU GCC Questions

[Gabriel Ravier]

On 7/8/23 13:46, Source Code via Gcc-help wrote:
> Hello dear GNU GCC team! I would like to ask you some questions:
> 1. Is GNU GCC completely free software? Can I use it for commercial and
> non-commercial projects without opening the source code?
> 2. Can I use GNU GCC on windows, linux and macOS? And at the same time not
> to use additional software, for example: Visual Studio?
> 3. Under what circumstances should I make my projects open source?
> 4. Can I use any headers in my projects? Or I should my projects open
> source?
>
> P.S. I really like your GNU GCC product and would really like to use it for
> C/C++ practice, maybe use it for commercial products in the future. But I
> really don't want to make my projects open source :)

1. Yes. Yes.

2. Yes. Yes.

3. If you're asking for my opinion on this, then obviously I'd say I'd 
quite like it if all programs were open source :p - but assuming you're 
asking under what circumstances usage of GCC would result in produced 
binaries being affected by its license, you should know that binaries 
produced by GCC are not covered by GCC's license in any way - you can 
freely use GCC to compile proprietary programs without any issues. The 
only way GCC's license could affect your program would be if you copied 
parts of GCC's source code into it (which is not something you'd 
normally do when just using GCC to compile programs)

4. Idk what you mean by "headers" but if you mean stuff like libstdc++ 
or the builtin headers, those have specific exceptions allowing you to 
use them in any program without any licensing implications.

Re: GNU GCC Questions

[Source Code]

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

This is great, thank you so much!

Сб, 8 июля 2023 г. в 17:53, Gabriel Ravier <gabravier@gmail.com>:

> On 7/8/23 13:46, Source Code via Gcc-help wrote:
> > Hello dear GNU GCC team! I would like to ask you some questions:
> > 1. Is GNU GCC completely free software? Can I use it for commercial and
> > non-commercial projects without opening the source code?
> > 2. Can I use GNU GCC on windows, linux and macOS? And at the same time
> not
> > to use additional software, for example: Visual Studio?
> > 3. Under what circumstances should I make my projects open source?
> > 4. Can I use any headers in my projects? Or I should my projects open
> > source?
> >
> > P.S. I really like your GNU GCC product and would really like to use it
> for
> > C/C++ practice, maybe use it for commercial products in the future. But I
> > really don't want to make my projects open source :)
>
> 1. Yes. Yes.
>
> 2. Yes. Yes.
>
> 3. If you're asking for my opinion on this, then obviously I'd say I'd
> quite like it if all programs were open source :p - but assuming you're
> asking under what circumstances usage of GCC would result in produced
> binaries being affected by its license, you should know that binaries
> produced by GCC are not covered by GCC's license in any way - you can
> freely use GCC to compile proprietary programs without any issues. The
> only way GCC's license could affect your program would be if you copied
> parts of GCC's source code into it (which is not something you'd
> normally do when just using GCC to compile programs)
>
> 4. Idk what you mean by "headers" but if you mean stuff like libstdc++
> or the builtin headers, those have specific exceptions allowing you to
> use them in any program without any licensing implications.
>
>
>