From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Raghavendra K <raghavendrak@myw.ltindia.com>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: C++ Support
Date: Fri, 20 May 2005 09:50:00 -0000 [thread overview]
Message-ID: <1116574872.10422.23.camel@localhost.localdomain> (raw)
In-Reply-To: <s28ce078.016@EMAIL>
On Thu, 2005-05-19 at 18:52 +0530, Raghavendra K wrote:
> Hi,
>
> Do we get STL support on ecos ( like vectors, queues etc). Also, we were trying out
> a simple application using iostream.h but ended up getting lot of errors during compilation.
> So we would like to know to what extent C++ is supported on ecos.
I'm using both STLport and libstdc++ w/eCos.
It isn't supported out of the box, but it isn't too hard to get it
working and I haven't seen any problems once up and running.
The instructions are a bit crude and there are some somewhat
questionable steps due to newlib/eCos issues, but you can always buy the
eCosPro kit if you want something that is fully tested and works out of
the box :-)
http://www.zylin.com/libstdc++.html
http://www.zylin.com/stlport.html
For the libstdc++ stuff I submitted a patch to eCos w.r.t. some issues
with using C++ early in eCos startup, but it didn't receive any comments
so far:
http://ecos.sourceware.org/ml/ecos-patches/2005-04/msg00007.html
--
Øyvind Harboe
http://www.zylin.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
next prev parent reply other threads:[~2005-05-20 7:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 15:08 [ECOS] " Raghavendra K
2005-05-19 15:58 ` [ECOS] setting up SLIP/PPP incoming connections Gonçalo Antunes
2005-05-20 2:14 ` Nick Garnett
2005-05-20 8:17 ` Gonçalo Antunes
2005-05-20 10:01 ` Nick Garnett
2005-05-19 19:40 ` Gonçalo Antunes
2005-05-20 9:50 ` Øyvind Harboe [this message]
2005-05-20 14:58 ` [ECOS] Re: C++ Support Jerome Souquieres
2005-05-21 8:30 ` Jonathan Larmour
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=1116574872.10422.23.camel@localhost.localdomain \
--to=oyvind.harboe@zylin.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=raghavendrak@myw.ltindia.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).