public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Uwe Kindler <uwe_kindler@web.de>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: ecos-devel@sourceware.org
Subject: Re: Just enough OS for eCos
Date: Sat, 08 Aug 2009 06:23:00 -0000	[thread overview]
Message-ID: <4A7D19C3.3020504@web.de> (raw)

Hello Sergei,

That is really a good idea. If I could put some things on the wish list 
that I would like to see in such an image ;O)


1. Precompiled toolchains for all architectures (or special JeCos for 
each architecture?)

2. The eCos Config GUI tool
I know that a lot of people use the command line tools. But especially 
for eCos beginners that download the VM image for eCos evaluation the 
GUI tool is easier to understand, to use and it helps to understand the 
eCos configuration system. And I know that there are also experienced 
eCos users (like me) that prefer the GUI tool.

3. A working docbook installation.
I did not even try to build the eCos dosumentation on a Windows machine 
and always switched to a Unbuntu VM to do this job.

4. A GUI debugger
I have to admit, I'm not a command line guru and I prefer GUI tools. I 
think if somone is familar with all the command line tools then he also 
has a running eCos linux environment. So it would be great to have a GUI 
debugger. I prefer Eclipse with Zylin CDT plugin.

6. A working synthetic target to play with eCos without real hardware

If you need some help testing stuff on a Windows XP machine I could help.

Regards, Uwe


             reply	other threads:[~2009-08-08  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08  6:23 Uwe Kindler [this message]
2009-08-08  7:10 ` Sergei Gavrikov
  -- strict thread matches above, loose matches on Subject: below --
2009-08-07 20:39 Sergei Gavrikov

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=4A7D19C3.3020504@web.de \
    --to=uwe_kindler@web.de \
    --cc=ecos-devel@sourceware.org \
    --cc=sergei.gavrikov@gmail.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).