From: "Davies, Greg" <Greg.Davies@Ultra-UEMS.com>
To: "ecos discuss" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] RE: System failure!!
Date: Sat, 26 Apr 2008 00:37:00 -0000 [thread overview]
Message-ID: <A25DBA3B0717824BAFD61F81242D5DBD011B9D1C@exchange.Ultra-UEMS.ca> (raw)
In-Reply-To: <48120B2D.5060008@ad-holdings.co.uk>
> Yes there's definately problems with this. Using the
> graphical tool, the tree is always regenerated if you use the
> tool to modify the config, but if something else modifies the
> ecc (eg your version control system brings in someone else's
> changes) then these changes might not get incorporated in your build.
In my case it was a combination of using the graphical tool, using
version control, the not-quite-production quality of the build
functionality in eclipse CDT, my laziness for not perfecting my build
process, and my abnormally high level of absent-mindedness, all coming
together in a perfect sotrm of one frustrating week of wasted time.
How about I make my post usefull in some way. If you're new to eCos, try
rebuilding eCos and your app from scratch right now. If it doesn't
recompile when you build from scratch, then be glad you caught the
problem sooner rather than later.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2008-04-25 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 15:38 [ECOS] " Alperen Coskun
2008-04-24 16:25 ` Gary Thomas
2008-04-25 16:48 ` Alperen Coskun
2008-04-25 14:24 ` Davies, Greg
2008-04-25 17:06 ` [ECOS] " Dave Lawrence
2008-04-26 0:19 ` Dave Lawrence
2008-04-26 0:37 ` Davies, Greg [this message]
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=A25DBA3B0717824BAFD61F81242D5DBD011B9D1C@exchange.Ultra-UEMS.ca \
--to=greg.davies@ultra-uems.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).