public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin cross-compiler on linux host
Date: Sun, 28 May 2017 18:41:00 -0000	[thread overview]
Message-ID: <2e5b96e4-4482-1833-a179-51ee4bde64d3@gmail.com> (raw)
In-Reply-To: <CAPF-yOaStHXroKaSvxoK9fXBx8EvrrnVW5sSnyRf=z-FWZGCxg@mail.gmail.com>

On 5/28/2017 11:13 AM, Dan Kegel wrote:
> On Sun, May 28, 2017 at 6:46 AM, Michele <michele.bucca@gmail.com> wrote:
>> 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 :)
> 
> What's wrong with mingw/MSYS?   

MSYS is nothing more than Cygwin and has nothing to do with the answer.

> Debian supports cross-compiling using

http://lmgtfy.com/?q=debian+windows+cross+compile

Or if you want to target Cygwin

http://lmgtfy.com/?q=debian+cygwin+cross+compile

> that, and the shell it comes with is deployable to windows xp, I
> think.

As long as you use only the XP supported API.  Otherwise it isn't likely
to work either.

-- 
cyg Simple

--
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

  reply	other threads:[~2017-05-28 15:47 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 [this message]
2017-05-28 22:30     ` Eliot Moss
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=2e5b96e4-4482-1833-a179-51ee4bde64d3@gmail.com \
    --to=cygsimple@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).