From: Alex Schuilenburg <alexs@ecoscentric.com>
To: Richard Rauch <rrauch@itrgmbh.de>, ecos-discuss@ecos.sourceware.org
Subject: Re: AW: AW: [ECOS] Re: eCos Configuration Tool clewan and rebuild
Date: Sat, 18 Jun 2016 13:20:00 -0000 [thread overview]
Message-ID: <57654A7A.6080206@ecoscentric.com> (raw)
In-Reply-To: <036101d1c959$16b15dd0$44141970$@itrgmbh.de>
On 18/06/16 13:01, Richard Rauch wrote:
> We delete the build folders only, but not the .ecc file.
> If rebuilding with GUI config tool (after build folders deleted) with same
> .ecc file, the result is exactly the same!
It ought to be - the same libcdl is called to regenerate the build tree
if you use the same .ecc file.
What I am saying is:
File->New in the anoncvs configtool
can generate a different configuration from the
ecosconfig new <target>
anoncvs command.
-- Alex
http://www.ecoscentric.com/ The eCos Experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2016-06-18 13:20 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
2016-06-18 12:01 ` AW: " Richard Rauch
2016-06-18 13:20 ` Alex Schuilenburg [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57654A7A.6080206@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=rrauch@itrgmbh.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).