public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: Richard Rauch <rrauch@itrgmbh.de>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Development environment under Windows without cygwin?
Date: Wed, 11 May 2011 16:06:00 -0000	[thread overview]
Message-ID: <4DCAB400.3060604@ecoscentric.com> (raw)
In-Reply-To: <3999221346CF4451878BF12BA616247D@DESKTOPITRGMBH>

On 2011-03-23 14:41, Richard Rauch wrote:
> Hi All,
>
> Do anybody knows a way to work without cygwin natively on Windows?

Yes, now we that we have formally announced native Windows host support :-)

The new 3.1 eCosPro Developers Kits (commercial versions of eCos, the
host tools and development environement) do not use cygwin at all.

ecosconfig and the GUI configtool shipped with eCosPro 3.1, as well as
all the GNU toolchains, run natively on all versions of Windows from XP
onwards, so you can stick with what you know.  Build times are also
comparable to those achieved on Linux hosts for same-spec machines. 

HTH
-- Alex


-- 
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:[~2011-05-11 16:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 15:55 Richard Rauch
2011-03-23 15:56 ` Gary Thomas
2011-03-23 16:20 ` Stanislav Meduna
2011-03-23 16:25   ` AW: " Richard Rauch
2011-03-23 16:28 ` [ECOS] " John Dallaway
2011-03-23 16:46 ` John Dallaway
2011-03-23 19:26 ` Grant Edwards
2011-03-23 22:46   ` AW: " Richard Rauch
2011-03-24  0:37     ` Michael Bergandi
2011-03-24  7:15       ` Grant Edwards
2011-03-24 10:59       ` Ilija Kocho
2011-03-24 14:32     ` Yurij Grechishhev
2011-05-11 16:06 ` Alex Schuilenburg [this message]
2011-05-13  9:30   ` [ECOS] " Manuel Borchers
2011-05-14 17:03     ` Alex Schuilenburg
2011-05-16 11:28       ` Manuel Borchers
2011-05-16 12:05         ` Alex Schuilenburg
2011-05-28 15:59           ` Manuel Borchers
2011-03-23 17:12 Guenter Ebermann

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=4DCAB400.3060604@ecoscentric.com \
    --to=alexs@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=rrauch@itrgmbh.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 read-only IMAP folder(s) and NNTP newsgroup(s).