public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jabran Bhatti <jabran.tlv@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: Building C++ application for eCos on ARM
Date: Mon, 02 Sep 2013 14:18:00 -0000	[thread overview]
Message-ID: <CAGujVxZ4Zo=WsjwEkpBJKg+CGV2YDBdK3fBegx=tsP3Gcyro5g@mail.gmail.com> (raw)
In-Reply-To: <521F730F.1090306@dallaway.org.uk>

Hi John,

Thanks for your answer, I will see what I can do with the uSTL library
and keep you posted.

Regards,

Jabran

2013/8/29 John Dallaway <john@dallaway.org.uk>:
> Hi Jabran
>
> On 29/08/13 15:33, Jabran Bhatti wrote:
>
>> I'm looking to build a C++ application for eCos on an ARM processor.
>> My program requires several standard C++ header files such as vector,
>> iostream, list, ...
>>
>> My question is: how can I achieve this? Does anyone have any
>> experience building and deploying C++ applications for eCos?
>
> Take a look at the eCos uSTL package which provides a size optimized
> implementation of most aspects of the C++ STL. Ref:
>
>   http://ecos.sourceware.org/docs-latest/ref/ustl-overview.html
>
> I hope this helps.
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john

-- 
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:[~2013-09-02 14:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 14:33 [ECOS] " Jabran Bhatti
2013-08-29 16:13 ` [ECOS] " John Dallaway
2013-09-02 14:18   ` Jabran Bhatti [this message]
2013-09-10 19:13     ` Jabran Bhatti
2013-09-11  8:03       ` John Dallaway
2013-09-17 14:41 cetoni GmbH - Uwe Kindler
2013-09-18 13:18 ` Jabran Bhatti
2013-09-18 17:14   ` Uwe Kindler

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='CAGujVxZ4Zo=WsjwEkpBJKg+CGV2YDBdK3fBegx=tsP3Gcyro5g@mail.gmail.com' \
    --to=jabran.tlv@gmail.com \
    --cc=ecos-discuss@sourceware.org \
    --cc=john@dallaway.org.uk \
    /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).