From: i.nixman@autistici.org
To: Oleksii Khramkov <oleksii.khramkov@globallogic.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC for Windows
Date: Sat, 17 Dec 2022 09:07:24 +0000 [thread overview]
Message-ID: <1bef7025277f9ae9bcb9f6276549f8c1@autistici.org> (raw)
In-Reply-To: <CAHe=5ECVAsD2=QzBtCW1-UZQCk0_6WQfpgnPVUiSK7b9pFVJHg@mail.gmail.com>
Hello,
just a two questions:
1) what is target OS/ARCH oft the compiled programs?
2) which additional third-party libs is required for the generated C
files to build?
best!
On 2022-12-17 08:10, Oleksii Khramkov via Gcc-help wrote:
> Dear Sir / Madam
>
> I am writing to request your help with the installation of GCC for
> Windows.
>
> I'm an embedded C developer and I have a task to adapt a python script
> for
> Windows that creates devise tree files for the required sample. Inside
> the
> script, GCC is called to compile C files. I never came across using GCC
> on
> Windows. Can you advise on how to install GCC for Windows, if it is
> possible?
>
> Thanks and best wishes,
>
> Yours faithfully,
>
> Oleksii Khramkov
next prev parent reply other threads:[~2022-12-17 9:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 8:10 Oleksii Khramkov
2022-12-17 9:07 ` i.nixman [this message]
[not found] ` <CAHe=5EB4KPGLFuYkZrB0ur-FbHAFm0z85qrvQe+gkc+sH=q40g@mail.gmail.com>
2022-12-21 7:42 ` i.nixman
2022-12-21 7:55 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2008-03-23 18:47 gcc for windows Freeman Gilmore
2008-03-23 19:06 ` Rodolfo Lima
2008-03-23 21:06 ` Tim Prince
2008-03-30 10:20 ` Sisyphus
2008-03-30 13:31 ` NightStrike
2008-03-31 7:25 ` Sisyphus
2008-03-31 10:17 ` Sisyphus
2000-03-30 13:00 GCC for Windows Owlex224
2000-03-30 15:46 ` Alexandre Oliva
2000-04-01 0:00 ` Alexandre Oliva
2000-03-30 21:27 ` Curtis R. Anderson
2000-04-01 0:00 ` Curtis R. Anderson
2000-04-01 0:00 ` Owlex224
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=1bef7025277f9ae9bcb9f6276549f8c1@autistici.org \
--to=i.nixman@autistici.org \
--cc=gcc-help@gcc.gnu.org \
--cc=oleksii.khramkov@globallogic.com \
/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).