public inbox for
 help / color / mirror / Atom feed
From: Grant Edwards <>
Subject: [ECOS] Re: eCos Configuration Tool clewan and rebuild
Date: Thu, 16 Jun 2016 21:41:00 -0000	[thread overview]
Message-ID: <njv6dn$ohb$> (raw)
In-Reply-To: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BF3@exchange>

On 2016-06-16, Michael W. Ellis <> wrote:

> Our approach in the past was to use the GUI tool but I agree that
> your approach is better since the script file more or less
> self-documents the process and is easily tracked under revision
> control.  Getting from the GUI based configuration to script based
> configuration requires some trial and error grunt work with file
> comparison tools to figure out exactly what options were changed in
> the GUI but it's probably worth it in the long run.

Yep, reverse-engineering a script from an existing .ecc file is a bit
of a chore, but I think it's probably worth it.  Like you said, it
takes a bit of of file comparison.  If enough work was done up-front
so that there's a template that includes the proper set of packages
it's possible that you won't need much more more than

  "ecosconfig new <whatever>"
  "ecosconfig tree"

... with perhaps a few option settings in between.

You can also add new templates or change existing ones so that you
have to do fewer "ecosconfig add" and "ecosconfig del" commands in
your script.  That's mostly a matter of personal taste.

> You asked what I meant by "cleaning".  The GUI tool basically has
> three build options: clean, library and tests.

Ah.  I don't know what exactly what the GUI does when you tell it to
"clean".  It might just do a "make clean", or it might remove
everything except the .ecc file and do an "ecosconfig tree".

BTW: I've been assuming you're doing development on a *nix host.  If
you're doing it under Windows+Cywgin, pretty much all the advise
applies, but you end up with a whole extra layer of possible issues
with Cygwin.

Grant Edwards               grant.b.edwards        Yow! An INK-LING?  Sure --
                                  at               TAKE one!!  Did you BUY any
                                COMMUNIST UNIFORMS??

Before posting, please read the FAQ:
and search the list archive:

  reply	other threads:[~2016-06-16 21:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-27 13:29 [ECOS] cyg_flag_timed_wait doesn't seem to work as expected Michael W. Ellis
2016-05-27 15:53 ` AW: " Richard Rauch
2016-05-27 16:31 ` Nick Garnett
2016-05-27 20:46   ` Michael W. Ellis
2016-06-16 13:26 ` [ECOS] eCos Configuration Tool clewan and rebuild Michael W. Ellis
2016-06-16 17:09   ` [ECOS] " Grant Edwards
2016-06-16 21:18     ` Michael W. Ellis
2016-06-16 21:41       ` Grant Edwards [this message]
2016-06-16 23:05         ` Alex Schuilenburg
2016-06-17  4:05           ` AW: " Richard Rauch
2016-06-17 10:10             ` Alex Schuilenburg
2016-06-18 12:01               ` AW: " Richard Rauch
2016-06-18 13:20                 ` Alex Schuilenburg
2016-06-30 14:53         ` [ECOS] Input from debug console Michael W. Ellis
2016-06-30 16:01           ` Michael W. Ellis
2016-06-30 16:09             ` Evgeniy Dushistov
2016-06-30 17:52             ` [ECOS] " 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='njv6dn$ohb$' \ \ \

* 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).