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

Actually we prefer to work with the GUI. .ecc Files are application  project
related. It is much more convenient to create the eCos configuration by
usage of GUI tool. We were working on all of our projects with the GUI
config tool.
We managed to create a version, not based on Cygwin as well. Regarding the
build library behavior, there should be no difference to the Cygwin version.

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.

Richard Rauch

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

  reply	other threads:[~2016-06-17  4: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
2016-06-17  4:05           ` Richard Rauch [this message]
2016-06-17 10:10             ` AW: " 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='030f01d1c84d$6d0cafc0$47260f40$' \ \ \

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