From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Vogel To: bartv@redhat.com Cc: Colin.Spier@pipinghotnetworks.com, ecos-discuss@sourceware.cygnus.com Subject: Re: [ECOS] C++ standard libraries Date: Wed, 13 Sep 2000 14:15:00 -0000 Message-id: <39BFEE83.782DF4DC@lightsurf.com> References: <39BF8BE9.B6793F2C@redhat.com> <200009131444.PAA01699@sheesh.cygnus.co.uk> X-SW-Source: 2000-09/msg00210.html We have successfully ported parts of the stdc++ (STL) library for eCos using the STLPort version and configuring no exceptions and no iostreams. It was a trivial (less than 1 day) port to do. The STLPort library is at http://www.stlport.org/ . -dave- Bart Veer wrote: > >>>>> "Jifl" == Jonathan Larmour writes: > > Jifl> Colin Spier wrote: > >> > >> Do you think that there is a significant amount of work involved? > >> > >> Where might one start? > > Jifl> I think it's several weeks worth of work. > > > > For more details on libstdc++ development and mailing lists you may > want to look at http://sources.redhat.com/libstdc++/ , although the > code has now been incorporated into the mainline gcc sources. > > Another possible concern is that eCos itself is currently compiled > with -fno-rtti -fno-exceptions. This could give problems if you start > mixing eCos and libstdc++ header files, since the latter will > definitely require exceptions and probably rtti as well. It is > possible that eCos will just work if you build it with rtti and > exceptions, but that is untested and obviously there would be some > code size penalties. > > Bart Veer // eCos net maintainer