public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: Developing for Cygwin from POSIX host
Date: Fri, 7 Aug 2020 09:24:56 +0100	[thread overview]
Message-ID: <DB7PR02MB3996E5DF9CD9940640D10674E7490@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <7d145537-d982-617c-7f2d-bb047a9d782b@SystematicSw.ab.ca>


[-- Attachment #1.1.1: Type: text/plain, Size: 895 bytes --]

On 07/08/2020 05:56, Brian Inglis wrote:
> 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 tried this a while back too, before I gave up and used a Windows VM.
Cygwin currently doesn't seem to work in wine, sadly. It does almost
work though, by the looks of it. I'm going to see if I can report some
bugs on WineHQ if any of the Wine developers are interested.

Hamish


[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-08-07  8:25 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
2020-08-07  8:24   ` Hamish McIntyre-Bhatty [this message]
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=DB7PR02MB3996E5DF9CD9940640D10674E7490@DB7PR02MB3996.eurprd02.prod.outlook.com \
    --to=hamishmb@live.co.uk \
    --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).