This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
AW: Re: eCos Configuration Tool clewan and rebuild
- From: "Richard Rauch" <rrauch at itrgmbh dot de>
- To: <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 17 Jun 2016 06:05:03 +0200
- Subject: AW: Re: eCos Configuration Tool clewan and rebuild
- Authentication-results: sourceware.org; auth=none
- References: <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50652 at exchange> <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BB3 at exchange> <njumgc$p71$1 at ger dot gmane dot org> <07FFDDED6CBCCE4E9FBD46AEC3EBFD4F02C50BF3 at exchange> <njv6dn$ohb$1 at ger dot gmane dot org> <576330BB dot 7080803 at schuilenburg dot org>
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 .\.......build and .\....install\. They
are located relative to your path, where the .ecc file is.
Richard Rauch
www.itrgmbh.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss