From: Stanislav Meduna <stano@meduna.org>
To: Richard Rauch <rrauch@itrgmbh.de>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Development environment under Windows without cygwin?
Date: Wed, 23 Mar 2011 16:20:00 -0000 [thread overview]
Message-ID: <4D8A0CBA.5090008@meduna.org> (raw)
In-Reply-To: <3999221346CF4451878BF12BA616247D@DESKTOPITRGMBH>
On 23.03.2011 15:41, Richard Rauch wrote:
> 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 ?
You can build yor own using MinGW. I am building such toolchains
regularly and the recent (4.4, 4.5) GNU ones are quite
friendly in this regard, although not completely without
problems. At our company these are used to build and link
applications against includes/libtarget built in a traditional
way - unfortunately there are people that are not comfortable
with configuring and running Linux and sending a setup
is easier than sending a virtual machine.
A major PITA is the slowness of Windows file status functions,
slowing make to a grind - the gcc/g++/libstdc++ build for
a mix of multilibs took several _days_.
I don't think it is possible to use a non-cygwin environment
to work with eCos itself - the time spent to make all the
makefiles etc. compatible would be IMHO enormous. Cygwin
is a mess, but finding workarounds will be less effort.
Regards
--
Stano
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2011-03-23 15:07 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 [this message]
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 ` [ECOS] " Alex Schuilenburg
2011-05-13 9:30 ` 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=4D8A0CBA.5090008@meduna.org \
--to=stano@meduna.org \
--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).