public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: cygwin cross-compiler on linux host
Date: Sun, 28 May 2017 22:30:00 -0000	[thread overview]
Message-ID: <e62afb48-3f4b-c600-3cf2-5e4bb949ccac@cs.umass.edu> (raw)
In-Reply-To: <EFFDB5CB-6B93-447B-BD45-F2F2F4463C83@gmail.com>

On 5/28/2017 9:46 AM, Michele wrote:
>
>
> Il 27 maggio 2017 20:25:45 CEST, Michele <michele.bucca@gmail.com> ha scritto:
>>
>>
>> Il 27 maggio 2017 20:22:46 CEST, Michele <michele.bucca@gmail.com> ha
>> scritto:
>>> I'm running Linux Debian as host and i would like to create a
>>> cross-compiler like mingw that uses cygwin.dll as libc, so I can
>>> compile software with POSIX support such as bash..is this possible?
>>
>> the target of course is a WINDOWS (XP) system.
>
> I know Windows XP it is now unsupported by cygwin and I apoligize for making such a question, but let's suppose I want to make a cross-compiler targeting a newer supported version of windows what should i do? Let's remember that I'm using Debian as host and the Windows system is the target :)

I would start here:

https://en.wikipedia.org/wiki/Cross_compiler#GCC_and_cross_compilation

Since gcc runs on cygwin, the gcc source includes support for cygwin as a target.
You will need to *build* gcc from source on your Debian platform, with cygwin as
the target.  (Note that there are 32-bit and 64-bit versions of cygwin.)  As the
wikipedia page points out, you will need to build binutils from source as well,
again with cygwin as the target.

In principle this is straightforward, though of course in practice any number of
difficulties might arise ...

Regards - Eliot Moss

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2017-05-28 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27 18:25 Michele
2017-05-27 18:31 ` Michele
2017-05-27 21:23   ` Dan Kegel
2017-05-28 15:13   ` Michele
2017-05-28 15:47     ` Dan Kegel
2017-05-28 18:41       ` cyg Simple
2017-05-28 22:30     ` Eliot Moss [this message]
2017-05-29  5:23 ` Brian Inglis

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=e62afb48-3f4b-c600-3cf2-5e4bb949ccac@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).