public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Slide <slide.o.mix@gmail.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] wxWidgets tool
Date: Mon, 01 Oct 2007 13:26:00 -0000	[thread overview]
Message-ID: <4700F56E.7060004@mlbassoc.com> (raw)
In-Reply-To: <a623f7d10710010620t1db9b23ekb5456c4c0720abf8@mail.gmail.com>

Slide wrote:
> On 10/1/07, Gary Thomas <gary@mlbassoc.com> wrote:
>> Slide wrote:
>>> I seem to remember someone saying that the wxWidgets based config tool
>>> is no longer supported and the command line tool is the way to go. Is
>>> there a howto document that takes someone familiar with the Windows
>>> tool and helps them understand how to do the same things with the
>>> command line tool?
>> You might be referring to the *old* Windows tool which was retired
>> many years ago (circa 1999) and replaced by the [more portable] wxWindows
>> based tool we have today.
>>
>> As for how to use the command line tool (ecosconfig), have you looked
>> at the documentation?
>>   http://ecos.sourceware.org/docs-latest/user-guide/using-ecosconfig-on-linux.html
>>
>> This applies to using ecosconfig on Windows (CygWin) as well as Linux.
>>
> 
> 
> Ah, I must be thinking of the old tool. Thanks for the info. If the
> wxWidgets tool is supported, patches will be accepted I assume?

Of course, send them to ecos-patches@ecos.sourceware.org
Did you have something in particular that needs work?

Please keep replies on the mailing lists so that all may benefit.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
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:[~2007-10-01 13:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  1:22 Slide
2007-10-01  8:32 ` [ECOS] " John Dallaway
2007-10-01  9:01 ` [ECOS] " Gary Thomas
     [not found]   ` <a623f7d10710010620t1db9b23ekb5456c4c0720abf8@mail.gmail.com>
2007-10-01 13:26     ` Gary Thomas [this message]
2007-10-01 14:04       ` Slide
2007-10-01 14:58         ` Tom Malcolmson
2007-10-01 15:03           ` Gary Thomas
2007-10-01 19:52             ` Tom Malcolmson
2007-10-02  8:30           ` [ECOS] " John Dallaway
2007-10-02  8:59             ` Lars Poeschel
2007-10-02 14:07             ` Andy Jackson

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=4700F56E.7060004@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=slide.o.mix@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).