public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: AW: [ECOS] Re: C++ Support
Date: Fri, 20 May 2005 13:36:00 -0000	[thread overview]
Message-ID: <5A8A17126B73AC4C83968F6C4505E3C5021A7D1D@JO-EX01.JENOPTIK.NET> (raw)

Hi,

> Von: ecos-discuss-owner@ecos.sourceware.org
...
> 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

Can you compare both ? Code size, execution speed, memory consumption, general impression, problems, etc. ?
 
> 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

I guess you should post again :-)

Bye
Alex

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2005-05-20  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 13:36 Neundorf, Alexander [this message]
2005-05-20 15:04 ` Øyvind Harboe

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=5A8A17126B73AC4C83968F6C4505E3C5021A7D1D@JO-EX01.JENOPTIK.NET \
    --to=alexander.neundorf@jenoptik.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=oyvind.harboe@zylin.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).