From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Developing for Cygwin from POSIX host
Date: Thu, 6 Aug 2020 22:56:47 -0600 [thread overview]
Message-ID: <7d145537-d982-617c-7f2d-bb047a9d782b@SystematicSw.ab.ca> (raw)
In-Reply-To: <9076494.QnH3kWR8HF@t450>
On 2020-08-06 19:58, John Scott via Cygwin wrote:
> I'm writing an application in C that's increasingly dependent on the POSIX
> APIs and would like to use the Cygwin DLL to help port it to Windows. I
> currently use MinGW-w64 but foresee that will stop being sufficient eventually.
>
> I want to do this using only free software without a Windows installation. A
> GNU/Linux to Cygwin cross compiler doesn't seem available, at least on Debian.
> Cygwin also fails to run under Wine.
Should work as there are fixes in each for the other.
> I'm not interested in the Cygwin userspace, I just need the POSIX layer. Aside
> from booting up a ReactOS VM, is there a more clean way to do what I seek to
> do?
There's a Fedora->Cygwin cross environment documented in:
https://cygwin.com/pipermail/cygwin/2020-July/245695.html
or your local copy from July 27-28.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-08-07 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 1:58 John Scott
2020-08-07 4:56 ` Brian Inglis [this message]
2020-08-07 8:24 ` Hamish McIntyre-Bhatty
2020-08-17 11:01 Hamish McIntyre-Bhatty
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=7d145537-d982-617c-7f2d-bb047a9d782b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).