From: Jonathan Larmour <jifl@eCosCentric.com>
To: nash dion <dion_nash_nz@yahoo.co.nz>
Cc: ecos-maintainers@sources.redhat.com
Subject: Re: Regarding applications and development tools
Date: Wed, 23 Jul 2003 12:23:00 -0000 [thread overview]
Message-ID: <3F1E7E58.1040805@eCosCentric.com> (raw)
In-Reply-To: <20030723102753.68693.qmail@web11507.mail.yahoo.com>
Hi,
nash dion wrote:
>
> We are in the process of analysis of different
> embedded operating systems for mobile devices like
> smartphones. We need valuable information regarding
> the different development tools
eCos uses the GNU tools. That means you develop with the editor of your
choice and the tools are all command line, although you can use insight if
you wish which is a graphical frontend to the GDB debugger. Some people
have reported instability with it so it is disabled by default with the
tools available with the default installation of eCos. Add "-w" to GDB's
arguments to see it.
If you want something more like a full integrated development environment
(IDE) then that's not something shipped with the default eCos. Instead you
need to contact companies that do commercial eCos support (see URL in my
sig for example, although there may be others who also do IDE support).
> and end user
> applications available with eCos Operating system.
I'm not quite sure what you mean here - it's up to you to write the
applications you want :-). Unless you mean things like web servers, SNMP
daemons etc. which eCos does have?
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
prev parent reply other threads:[~2003-07-23 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 10:28 nash dion
2003-07-23 12:23 ` Jonathan Larmour [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=3F1E7E58.1040805@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=dion_nash_nz@yahoo.co.nz \
--cc=ecos-maintainers@sources.redhat.com \
/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).