linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pete McCormick <pete261@yahoo.com>
To: John.Fisher@nec.com.au, linuxppc-embedded@lists.linuxppc.org
Subject: RE: cygwin and embedded linux
Date: Wed, 21 Aug 2002 20:20:58 -0700 (PDT)	[thread overview]
Message-ID: <20020822032058.73464.qmail@web9501.mail.yahoo.com> (raw)
In-Reply-To: <000501c24979$6348a190$37d34c93@neca.nec.com.au>


> So what are the issues: How is cygwin significantly different from Linux
> that you would not want to use it?
> Are there useful tools that run under Linux but not under cygwin?
> The reason I ask is that my organization currently does its software
> development under windows using proprietary tools. We have to maintain our
> existing products using these tools. We are however contemplating new
> development using linux. If we have to dual boot our PCs or have an extra PC
> running Linux for each developer, that is going to bring its own set of
> nuisances and problems.

I am in a very similar situation as you.  I had a few problems doing things in
cygwin, things not building correctly, no genksyms for the kernel modules,
mount doesn't have all the options that the linux version does (for example
loopback file systems, useful for creating a ramdisk image.), etc.  So I feel
it is less desirable than a linux environment.

The solution that I am trying to implement in my current company is to do the
cross compiling on actual linux servers, using telnet or ssh from the windows
machines.  Running samba on the linux servers will let the windows people use
their current favorite programmer's editors.  If you install cygwin on the
windows machines, you can use their xwindows client Cygwin/XFree86 to run gui
applications remotely, if desired (e.g. DDD or Insight debuggers).


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

  reply	other threads:[~2002-08-22  3:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-21  7:58 cygwin and embedded linux John Fisher
2002-08-21 14:54 ` Magnus Damm
2002-08-21 15:54 ` Marius Groeger
2002-08-22  1:15   ` John Fisher
2002-08-22  3:20     ` Pete McCormick [this message]
2002-08-22  6:56     ` Wolfgang Denk
2002-08-23  0:05       ` Dr. Craig Hollabaugh
2002-08-22  7:36     ` Marius Groeger
2002-08-23 13:13       ` Marius Groeger
2002-08-22 11:00     ` Magnus Damm
2002-08-23 13:10       ` Jerry Van Baren
     [not found]     ` <Pine.LNX.4.40.0208220914420.2118-100000@mag.devdep.sysgo.d e>
2002-08-22 23:39       ` Dr. Craig Hollabaugh
2002-08-23  5:18         ` Dan Malek
2002-08-23  7:03           ` Dr. Craig Hollabaugh
2002-08-23  9:34           ` Kenneth Johansson
2002-08-24  0:11             ` Dan Malek
2002-08-27 10:24               ` Sangmoon Kim
2002-08-23  9:15         ` Magnus Damm
2002-08-23 12:56         ` Jerry Van Baren
2002-08-23  5:03     ` Dan Taylor
  -- strict thread matches above, loose matches on Subject: below --
2002-08-21 15:07 Steven Blakeslee
2002-08-22 13:06 Hihn Jason
2002-08-22 23:48 Kerl, John
2002-08-22 23:50 Kerl, John

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=20020822032058.73464.qmail@web9501.mail.yahoo.com \
    --to=pete261@yahoo.com \
    --cc=John.Fisher@nec.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).