public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Dirk Husemann <hud@zurich.ibm.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] eCos Configuration Tool
Date: Mon, 19 Sep 2005 14:37:00 -0000	[thread overview]
Message-ID: <20050919092955.GA24142@lunn.ch> (raw)
In-Reply-To: <432E75B3.1040508@zurich.ibm.com>

> >I think the configtool is more to keep the commercial clients happy
> >where the management people have a percieved need for a "friendly GUI"
> >when they buy eCos from the companies that give commercial support. I
> >don't remember anybody actually contributing patches for the
> >configtool, so from an open source perspective, the configtool is
> >dead. The RTOS is what people are interested in, not the tools needed
> >to configure it.
> > 
> >
> actually, no. in my experience, both tools and embeddedOS are what ppl 
> are interested in. some developers are more comfortable with 
> commandline, some like GUI, some use both (i find it easier to find 
> things/options in configtool).

I worded that badly. What i ment was developers are interested in
developing the RTOS further. Lots of people contribute patches for the
RTOS. Nobody seems interesting in developing the tools further. Nobody
contributes patchs for the tools.

> also, while i'm at it :-) both configtool and ecosconfig copy header 
> files into the install tree, it would be extremely helpful if we could 
> have an option to symlink instead --- why? well, debugging with GDB 
> within emacs: gdb ends up using the correct .c files, but unfortunately 
> uses the copied .h files, nasty if you spot a bug in the .h file, fix it 
> and then are surprised that the bug fix disappeared (because it was made 
> to a header file in the install tree and not in the originating ecos tree).

I've fallen faul of the same problem once or twice until i got used to
it. Well this is a good chance to show that people are interested in
to the tools. Please contribute a patch to add this feature to the
tools :-)
        
        Andrew

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

  reply	other threads:[~2005-09-19  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18 22:13 Emilio Monti
2005-09-19  2:32 ` Andrew Lunn
2005-09-19  7:44   ` Emilio Monti
2005-09-19  9:30   ` Andrew Voelkel
2005-09-19 12:54   ` Dirk Husemann
2005-09-19 14:37     ` Andrew Lunn [this message]
2005-09-19 15:59     ` [ECOS] " John Dallaway
  -- strict thread matches above, loose matches on Subject: below --
2001-07-19  8:45 [ECOS] " diem.b.dang
2001-07-19 12:10 ` Jonathan Larmour

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=20050919092955.GA24142@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=hud@zurich.ibm.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).