From: Patrick Huesmann <patrick.huesmann@gmail.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: cross-compiling under cygwin?
Date: Fri, 08 Apr 2005 19:57:46 +0200 [thread overview]
Message-ID: <4256C61A.3030205@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504081010330.14089@localhost.localdomain>
Hi,
Robert P. J. Day wrote:
> i've just had a request from a colleague who wants to do all the
>cross-compilation for our 8xx board on a windows box, rather than
>linux.
>
> there was talk of cygwin, and kdevelop as well. i'm still parsing
>the rest of the email but is there a canonical URL that discusses
>working in the windows environment?
>
>
We use colinux (http://www.colinux.org) for that. It's a Linux kernel
that runs as application under windows. It shares networking with the
windows system so you can operate it via telnet or ssh. You can even run
IDEs like kdevelop as remote X application and use the cygwin's X window
system to use the Linux apps under windows.
Before that, we used VMware, but coLinux is free and IMO, it has better
performance because it doesn't have to simulate a whole computer (but
only a small hardware abstraction layer).
It comes with a pre-patched Debian image which gives you a minimal Linux
installation. From there you set up the networking, and simply apt-get
install your apps like you would do with a native Linux box.
HTH,
Patrick
next prev parent reply other threads:[~2005-04-08 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 14:13 cross-compiling under cygwin? Robert P. J. Day
2005-04-08 14:46 ` Tom Rini
2005-04-08 16:49 ` Wolfgang Denk
2005-04-08 16:52 ` Robert P. J. Day
2005-04-08 17:57 ` Patrick Huesmann [this message]
2005-04-08 18:32 ` Dan Malek
2005-04-08 18:35 ` Robert P. J. Day
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 15:24 Steven Blakeslee
2005-04-08 18:48 Howard, Marc
2005-04-08 21:17 ` Dan Malek
2005-04-10 16:59 ` Wolfgang Denk
2005-04-11 18:30 Howard, Marc
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=4256C61A.3030205@gmail.com \
--to=patrick.huesmann@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.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 NNTP newsgroup(s).