linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Cross Compiler running under Win32
Date: Wed, 26 Nov 2003 19:19:00 -0800	[thread overview]
Message-ID: <3FC56D24.6030000@kegel.com> (raw)
In-Reply-To: <3FC4B0EC.3090107@imc-berlin.de>


Steven Scholz wrote:
> does someone know of a cross compiler (producing code for let's say MPC8xx) that
> is running natively under win32 (Windows2000/XP) without stuff like CYGWIN?
>
> I'am just wondering.
> Apparently MVISTA released their new "DevRocket" which is supposed to
> run under
> WindowsXP. So I assume they have cross compilers for "30 processors from 8
> architectures" running under Windows...

They could well be using cygwin for the compilers; they charge
enough that the licensing fee for cygwin is peanuts, I bet.

But what's wrong with using Cygwin?

Answering my own question, it's a bit of a challenge to use
cygwin in an installed package because there are fairly
frequent incompatibilities introduced in the cgywin dll,
so if the user installs a newer or older version than you
expect, your installed package won't work.  It's rather
maddening.  And it seems there's no way to 'embed' cygwin
in such a way that it uses a private copy of the cygwin dll.
- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-11-27  3:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 13:55 Cross Compiler running under Win32 Steven Scholz
2003-11-26 18:52 ` Nathan Field
2003-11-27  3:19 ` Dan Kegel [this message]
2003-11-27 10:18   ` Steven Scholz
2003-11-27 17:16     ` Dan Kegel
2003-12-01 18:26 ` Mark A. Greer

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=3FC56D24.6030000@kegel.com \
    --to=dank@kegel.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.de \
    /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 NNTP newsgroup(s).