From: John Dallaway <jld@codeconfidence.com>
To: eCos Announcements <ecos-announce@ecos.sourceware.org>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [COMMERCIAL] Code Confidence announces Eclipse-based IDE for eCos developers
Date: Fri, 20 Nov 2009 15:14:00 -0000 [thread overview]
Message-ID: <4B068AEE.5020300@codeconfidence.com> (raw)
Code Confidence Ltd is launching the Code Confidence Tools for eCos this
week.
Based on the award-winning Eclipse(tm) Platform and C/C++ Development
Tooling (CDT), the Code Confidence(tm) Tools provide a fully-integrated
development environment for application developers working with the
eCos(R) real-time operating system.
"We've designed the tools to maximise productivity at all levels"
explained John Dallaway, Director at Code Confidence. "Everything
necessary for eCos configuration, application building and remote
debugging is available for rapid download and installation from within
the Eclipse workbench - allowing developers to focus on their own code
from day one."
Product features include:
* Simplified eCos project creation using software wizards
* An advanced eCos configuration editor for rapid comprehension and
customisation of operating system features
* Full integration with the CDT source code editor including syntax
highlighting, content assistance and navigation of both eCos and
application source code
* An optimised eCos build system with robust file dependency analysis
* A remote debugging launcher for application download and debugging
on embedded hardware
* All necessary GNU toolchain components - built for high performance
(Cygwin not required)
The Code Confidence Tools for eCos are available on both Windows and
Linux development hosts. For further details, visit the Code Confidence
website: http://www.codeconfidence.com/tools
--
John L Dallaway
Code Confidence Ltd
http://www.codeconfidence.com
reply other threads:[~2009-11-20 15:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B068AEE.5020300@codeconfidence.com \
--to=jld@codeconfidence.com \
--cc=ecos-announce@ecos.sourceware.org \
--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).