public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ram Sudhir Tadavarthi" <ram.tadavarthi@netco.de>
To: <ecos-discuss@ecos.sourceware.org>
Subject: AW: [ECOS] Ecosconfig and configtool
Date: Wed, 10 May 2006 08:37:00 -0000	[thread overview]
Message-ID: <20060510082302.7ADB6213B5F@gemmini.netco.de> (raw)
In-Reply-To: <4461A376.9040205@webdyn.com>

Hi,

Configtool is Graphical tool and ecosconfig is command line tool. You can
use either as per your convenience. I prefer to use configtool. IMHO both
should provide same results though I never tried to use ecosconfig tool
much.

Warm regards,
ram

-----Ursprüngliche Nachricht-----
Von: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] Im Auftrag von Emmanuel
Viollet
Gesendet: Mittwoch, 10. Mai 2006 10:25
An: ecos-discuss@ecos.sourceware.org
Betreff: [ECOS] Ecosconfig and configtool

Hi.

Under Windows, which tool am I supposed to use? ecosconfig or configtool?
I see that the two tools do not produce the same results (different 
directory structures for instance).
Is this normal?

In advance, thanks.

-- 
Emmanuel Viollet
Software engineer
Webdyn
e-mail : Emmanuel.Viollet@webdyn.com
Tel    : +33 (0)1 39 04 29 55


-- 
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

  parent reply	other threads:[~2006-05-10  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  8:25 Emmanuel Viollet
2006-05-10  8:34 ` Andrew Lunn
2006-05-10  8:37 ` Ram Sudhir Tadavarthi [this message]
2006-05-10  8:48   ` AW: " Emmanuel Viollet
2006-05-10  9:12     ` Andy Jackson
2006-05-10 10:19       ` Emmanuel Viollet

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=20060510082302.7ADB6213B5F@gemmini.netco.de \
    --to=ram.tadavarthi@netco.de \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).