public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Source Code <rifesourcecode@gmail.com>
To: Gabriel Ravier <gabravier@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GNU GCC Questions
Date: Sat, 8 Jul 2023 17:57:34 +0600	[thread overview]
Message-ID: <CA+=F_brrATsfSmCcuXH=bbdzVMb-P9ojaVQ+=p5NtEb2u1SvFg@mail.gmail.com> (raw)
In-Reply-To: <8cfa6e17-6b8b-03f5-71be-eab86b047072@gmail.com>

[-- 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.
>
>
>

      reply	other threads:[~2023-07-08 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08 11:46 Source Code
2023-07-08 11:53 ` Gabriel Ravier
2023-07-08 11:57   ` Source Code [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+=F_brrATsfSmCcuXH=bbdzVMb-P9ojaVQ+=p5NtEb2u1SvFg@mail.gmail.com' \
    --to=rifesourcecode@gmail.com \
    --cc=gabravier@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).