public inbox for
 help / color / mirror / Atom feed
From: Alex Schuilenburg <>
Subject: Re: AW: [ECOS] Re: eCos Configuration Tool clewan and rebuild
Date: Fri, 17 Jun 2016 10:10:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <030f01d1c84d$6d0cafc0$47260f40$>

On 17/06/16 05:05, Richard Rauch wrote:
> There is one issue maybe. When we are changing major things in our eCos
> configuration, we delete the complete build tree folders with file system.
> Then the config tool is forced to rebuild everything.
> The folders are somehow named like .\ and .\....install\. They
> are located relative to your path, where the .ecc file is.
These are created <basename>_install and <basename>_build where
<basename> is the base name of the saved .ecc file.

Yes, when using the anoncvs GUI configtool the safest method when
changing configurations is to delete all and rebuild.

However, the anoncvs GUI configtool has a subtle major flaw when
creating a configuration by selecting a target that is not the default.
All new target configurations are created against the current target and
template (often default target and "default" template), and switched to
the new target (and/or template).  If you have two similar but distinct
targets you could end up with conflicts that the anoncvs GUI tool cannot
resolve automatically.  Even creating a new configuration for the
default target can and often does result in a slightly different
configuration (but entirely valid) to that created by ecosconfig.

If you are using the anoncvs tools, the safest way to create a new
configuration is to use "ecosconfig" - it is the tool that almost all
eCos maintainers outside eCosCentric use.

eCosPro users should upgrade to version 3.1.10 of the Host Tools which
exhibit none of the anoncvs host tools issues - new configurations
created by both tools are identical - and use the "File->New Target"
functionality illustrated in

-- Alex             The eCos Experts

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

  reply	other threads:[~2016-06-17 10:10 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
2016-06-17  4:05           ` AW: " Richard Rauch
2016-06-17 10:10             ` Alex Schuilenburg [this message]
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).