AW: [ECOS] Development environment under Windows without cygwin?

Richard Rauch rrauch@itrgmbh.de
Wed Mar 23 17:43:00 GMT 2011


Hi again

I have found now an interesting link: http://ecos.sourceware.org/ct2.html 

Is that, what I'm searching for? I have read the description and it looks
like that this version of the Configuration Tool is running without cygwin?
But the page itself is marked as "obsolete". So maybe this work was not
continued?

How knows more about this?


Richard

Richard Rauch
email: rrauch@itrgmbh.de
 
_______________________________________________

ITR GmbH 
Informationstechnologie Rauch 
Schnepfenreuther Hauptstrasse 27b
D-90425 Nuernberg
 
phone:  +49 (0) 911 3784437
VoIP:    +49 (0) 911 495221739
web:     http://www.itrgmbh.de
email:   info@itrgmbh.de
 
Geschaeftsfuehrer: Richard Rauch
Handelsregister: Nuernberg HR B 21676
USt-Id Nr. : DE228051873
_______________________________________________

-----Ursprüngliche Nachricht-----
Von: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] Im Auftrag von Guenter
Ebermann
Gesendet: Mittwoch, 23. März 2011 17:21
An: rrauch@itrgmbh.de
Cc: ecos-discuss@ecos.sourceware.org
Betreff: Re: [ECOS] Development environment under Windows without cygwin?

Hi,

> Do anybody knows a way to work without cygwin natively on Windows?
>
> It seems, that cygwin is causing several problems on different windows 
> environments.
> Is there a way to work without cygwin?
> Is the gnu compiler/linker toolchain available for windows? Which 
> versions are comparable to the arm-eabi-gcc V4.3.2 ?
> Is it possible to run the eCos Config Tool without cygwin?

We use the same linux VM on all our developer work stations under a windows
host at the moment. Also for building eCos. No Problems so far.

In the past we also maintained a cygwin-free mingw-based gcc/make
Buildenvironment. But only building ecos applications, not eCos itself.

If you have problems with the moving cygwin target you can also setup local
cygwin repositories with a fixed version where all developers get their
cygwin from.

Best solution for us was the linux VM. Least trouble.

best regards,
Guenter

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



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



More information about the Ecos-discuss mailing list