This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: c++ libraries
- From: Matthew Jones <matthewjones at vw1600e dot org dot uk>
- To: newlib at sources dot redhat dot com
- Cc: Craig Edwards <craig at haenterprises dot com dot au>
- Date: Thu, 21 Apr 2005 08:46:09 +0100
- Subject: Re: c++ libraries
- References: <opspkhe0011jf2l8@edwardsc.cf1.au.ibm.comau.ibm.comibm.com>
Quoting Craig Edwards <craig@haenterprises.com.au>:
> I recently ported the newlib libraries to work on the XBOX and would like
> to add C++ support. Now, I've looked around, and to be honest, am very
> confused about what I need to port so that it will work with my newlib
> port. Do I somehow need to extract the libstdc++ stuff from gcc? I
> thought STL might have been a good place to start, but the SGI STL stuff
> seems to just be a collection of header files.
>
> Sorry for the newbish-ness of the question... I am just confused! Any
> advice would be much appreciated. Thanks a lot.
For just the language support, you are on the right track - get libstdc++ built,
then link with libsupc++, the C++ language support library. I am doing exactly
this, with newlib, for a PowerPC target.
Take care with crt0 and the linker script - there are C++ aspects to both. The
default linker script that gcc produces is a good starting point.
For full STL you need all the headers, and libstdc++.
--
Matthew JONES
http://www.tandbergtv.com/