From: Gary Thomas <gary@mlbassoc.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: eCos configuration question (was Re: [ECOS] General Q ...)
Date: Thu, 31 May 2007 17:30:00 -0000 [thread overview]
Message-ID: <465F04CB.3030302@mlbassoc.com> (raw)
In-Reply-To: <013401c7a3a7$9ddf46f0$887ba8c0@PAULD>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Paul D. DeRocco wrote:
>> From: Grant Edwards
>>
>> I don't think any of the "pros" do. AFAICT, it's just
>> eye-candy to lessen the initial culture shock for Visual-C
>> programmers. ;)
>
> Other than just a hackish preference for command lines, is there anything
> that ecosconfig can do that configtool can't? The latter seems pretty
> useful, as it lets you see all the documentation on options that is
> otherwise scattered around a million .cdl files.
>
I for one rarely do anything that I can't script. ecosconfig
works perfectly for this, the configtool does not. For example,
I may build as many as 128 (or more) versions of RedBoot at
one time, each requiring its own configuration, build tree, etc.
If I *had* to do this with the GUI, I'd never get my work done!
- --
- ------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
- ------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGXwTLmaKbSsQGV8ARAlEZAJ0elS7bIcQJzMakGbnjmG525LtbQgCeJVxx
qq5xo4CJKVxOdYoOt0dz1GQ=
=wt5f
-----END PGP SIGNATURE-----
--
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:[~2007-05-31 17:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 17:02 [ECOS] General Q: Calling RedBoot CLI function from eCos app John Mills
2007-05-30 17:12 ` Gary Thomas
2007-05-30 17:16 ` Andrew Lunn
2007-05-30 17:20 ` Andrew Lunn
2007-05-30 17:58 ` John Mills
2007-05-30 19:18 ` John Mills
2007-05-30 21:00 ` Andrew Lunn
2007-05-30 21:06 ` John Mills
2007-05-30 21:41 ` Andrew Lunn
2007-05-31 15:01 ` [ECOS] eCos configuration question (was Re: [ECOS] General Q ...) John Mills
2007-05-31 15:19 ` Gary Thomas
2007-05-31 15:21 ` John Mills
2007-05-31 15:21 ` [ECOS] " Andrew Lunn
2007-05-31 16:41 ` Grant Edwards
2007-05-31 17:09 ` [ECOS] Re: eCos configuration question Sergei Organov
2007-05-31 17:24 ` [ECOS] Re: eCos configuration question (was Re: [ECOS] General Q ...) Paul D. DeRocco
2007-05-31 17:30 ` Gary Thomas [this message]
2007-05-31 17:35 ` Grant Edwards
2007-05-31 19:01 ` Andrew Lunn
2007-05-31 17:18 ` [ECOS] " Sergei Gavrikov
2007-06-01 8:10 ` [ECOS] Re: eCos configuration question Daniel Néri
2007-06-01 9:04 ` Sergei Gavrikov
2007-06-01 14:23 ` Grant Edwards
2007-06-01 14:30 ` Gary Thomas
2007-06-01 14:37 ` Grant Edwards
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=465F04CB.3030302@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=pderocco@ix.netcom.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).