public inbox for
 help / color / mirror / Atom feed
From: Alex Schuilenburg <>
Subject: Re: [ECOS] Re: eCos Configuration Tool clewan and rebuild
Date: Thu, 16 Jun 2016 23:05:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <njv6dn$ohb$>

On 16/06/16 22:41, Grant Edwards wrote:
> [...]
> Ah. I don't know what exactly what the GUI does when you tell it to
> "clean". It might just do a "make clean",

That is exactly what it does.

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

The anoncvs version of GUI configtool is broken when it comes to
dependencies, the handling of templates, and even creating a new target
configuration.  In fact the ordering of the appearance of dependencies
within CDL could change the configuration you ended up with as a result
of the way that the anoncvs GUI configtool resolves dependencies.

Using anoncvs ecosconfig is the better solution as you state, but it too
has issues with dependencies so you are recommended to "make clean",
"ecosconfig tree", and "make" to ensure everything is built from the
correct headers and makefiles.

FWIW, the issues with these tools have been been resolved within the
eCosPro host tools since eCosPro 3.1.X (including dropping cygwin
entirely) and the GUI configtool has become very useful but
unfortunately these changes have not made their way back into anoncvs.

-- Alex             The eCos Experts

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

  reply	other threads:[~2016-06-16 23:05 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
2016-06-16 23:05         ` Alex Schuilenburg [this message]
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 \ \ \ \

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