public inbox for
 help / color / mirror / Atom feed
From: "Michael W. Ellis" <>
To: <>
Subject: RE: [ECOS] Re: eCos Configuration Tool clewan and rebuild
Date: Thu, 16 Jun 2016 21:18:00 -0000	[thread overview]
Message-ID: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BF3@exchange> (raw)
In-Reply-To: <njumgc$p71$>

> -----Original Message-----
> From: [mailto:ecos-discuss-
>] On Behalf Of Grant Edwards
> Sent: Thursday, June 16, 2016 12:10 PM
> To:
> Subject: [ECOS] Re: eCos Configuration Tool clewan and rebuild
> On 2016-06-16, Michael W. Ellis <> wrote:
> > I have inherited a project based on eCos 2.0.98 and have reached a
> > point where I need to rebuild my library.  Most of the folks who
> > originally worked on this project are no longer with the company and
> > our internal documentation is scarce at best.
> >
> > My understanding is that the eCos Configuration Tool is used to make
> > changes to a .ecc file, and then to use this file to build the
> library.
> Yes.  However, there are two different ecos configuration tools.  A
> command line one, and a GUI one (there might be multiple similar but
> different look/feel GUI ones, I don't really know).
> For all our actuall production code, we use the command-line
> utility exclusivly.  That way you can write a shell script that calls
> the ecosconfig utility to generate an .ecc file from scratch and then
> creates the build tree.
> That shell script is then placed under source control just like the
> rest of source code.  IMO, relying on a GUI tool and
> accurate/repeatable human clicking for building production code is a
> huge mistake.  You can place the .ecc file under version control if
> want, but (IMO) it's far more important that the script that _builds_
> the .ecc file is under source control.

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.

You asked what I meant by "cleaning".  The GUI tool basically has three
build options: clean, library and tests.  I had tried using the build
clean option, expecting it to remove all intermediate and output files
(including my linker file) but this didn't seem to do what I expected.

Thanks for the tips.  This has helped clarify the situation immensely.


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

  reply	other threads:[~2016-06-16 21:18 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 [this message]
2016-06-16 21:41       ` Grant Edwards
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=07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BF3@exchange \ \ \

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