public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: eCos on Windows without Cygwin
Date: Thu, 01 Mar 2007 18:33:00 -0000	[thread overview]
Message-ID: <es768s$e04$1@sea.gmane.org> (raw)
In-Reply-To: <c09652430703010523u18dca526r6e107a997466e3d2@mail.gmail.com>

On 2007-03-01, Øyvind Harboe <oyvind.harboe@zylin.com> wrote:

> If you don't agree that the dependence on Cygwin is hampering eCos,
> then don't read further.

Windows+Cygwin may indeed suck (IMO Windows+<anything> sucks).
Just do the right thing and install Linux. ;)

Windows+Cygwin is a royal pain, but it's probably not going
away.  The tools Altera supplies for it's new 32-bit CPU
(NIOS2) are purely Eclipse+GCC based. On Windows, they ship
enough of Cygwin along with it to create something that almost
works.

Rathing than stating that "the dependence on Cygwin is hapering
eCos", I prefer to say that "the availability of eCos tools for
Cygwin is widening its audience.

> Problems w/Cygwin:

[lots of problems w/ Cygwin]

Yup, Cygwin sucks compared to a real Unix system.  So use a
real Unix system.

> As far as I know, MinGW binaries of GCC toolchains + eCos tools is the
> most tantalizing prospect.

Except the eCos tools require a lot of support stuff (TCL,
bash shell, etc.).  I don't see how MinGW binaries of GCC
toolchains are going to allow you to run fairly complex TCL and
bash programs.

> Since a eCos needs are so simple & unchanging,

eCos needs aren't really all that simple.

> I believe a MinGW based package could live relatively
> unchanged for years.
>
> Does anyone know of any organized efforts to address these
> problems?

I don't really see how it could work.

-- 
Grant Edwards                   grante             Yow!  My ELBOW is a remote
                                  at               FRENCH OUTPOST!!
                               visi.com            


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2007-03-01 18:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 13:24 [ECOS] " Øyvind Harboe
2007-03-01 13:41 ` Mikael Helbo Kjær
2007-03-01 14:19 ` Andrew Lunn
2007-03-01 14:25   ` Øyvind Harboe
2007-03-01 17:47     ` Kevin Wilson
2007-03-01 18:40     ` [ECOS] " Grant Edwards
2007-03-01 20:35       ` Donald Walton
2007-03-02  7:24         ` [ECOS] creating flash partitions in uBoot jatinder
2007-03-02 11:56           ` Gary Thomas
2007-03-02  9:18     ` [ECOS] eCos on Windows without Cygwin Ilija Koco
2007-03-02  9:27       ` Øyvind Harboe
2007-03-02 16:52         ` Ilija Koco
2007-03-02 17:01           ` Alexander Neundorf
2007-03-02 17:50             ` [ECOS] " Grant Edwards
2007-03-02 17:00         ` Grant Edwards
2007-03-03  6:20         ` [ECOS] eCos on Windows without Cygwin - try SFU ;) rtos
2007-03-01 15:28 ` [ECOS] eCos on Windows without Cygwin Tom Malcolmson
2007-03-01 18:33 ` Grant Edwards [this message]
     [not found] ` <c09652430703010523u18dca526r6e107a997466e3d2@mail.gmail.co  m>
2007-03-02  7:19   ` Chuck McManis

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='es768s$e04$1@sea.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.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).