public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Åke Rehnman" <ake.rehnman@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Using ARM GNU GCC with Cygwin
Date: Sat, 4 Apr 2020 20:58:15 +0200	[thread overview]
Message-ID: <38a47b9b-f43a-3727-2205-f02f0dbd48d0@gmail.com> (raw)
In-Reply-To: <51717d4a9c861fd90b5f9a58b84b308a@mail.kylheku.com>


On 2020-04-04 16:32, Kaz Kylheku via Cygwin wrote:
> On 2020-04-04 02:00, Ben wrote:
>> Is there something else I'm missing?
>
> That by cross-compiling for your targets on Cygwin instead of a real 
> POSIX OS, you will something like double your compile times, if not more.
>
> Why would you involve Cygwin in a development activity whose target 
> isn't POSIX on Windows.

Most strange comment I have read... With your reasoning why bother with 
cygwin at all for any reason?

I do cross compiling all the time in cygwin and the reason is of course 
to not have to deal with windows paths and what not plus you have access 
to all the build tools like make binutils grep sed autotools.



  parent reply	other threads:[~2020-04-04 18:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04  9:00 Ben
2020-04-04 10:23 ` Eliot Moss
2020-04-04 18:15   ` Ben
2020-04-04 14:32 ` Kaz Kylheku
2020-04-04 18:18   ` Ben
2020-04-04 18:58   ` Åke Rehnman [this message]
2020-04-04 19:10     ` Ben
2020-04-04 20:39       ` Marco Atzeri
2020-04-08 20:50     ` Kaz Kylheku
2020-04-08 20:58       ` David Rothenberger
2020-04-08 21:13         ` Ben Kamen
2020-04-09  0:33           ` Kaz Kylheku
2020-04-09  0:17         ` Kaz Kylheku
2020-04-04 21:40   ` Andrey Repin
2020-04-04 21:56     ` Eliot Moss
2020-04-05  8:49     ` Csaba Raduly
2020-04-07 17:36       ` Ben
2020-04-04 19:11 ` Åke Rehnman
2020-04-04 19:31   ` Åke Rehnman

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=38a47b9b-f43a-3727-2205-f02f0dbd48d0@gmail.com \
    --to=ake.rehnman@gmail.com \
    --cc=cygwin@cygwin.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).