Re: stlport v/s libstdc++

[mfletcher at serck-controls dot co dot uk]

>I have been wondering about the pros/cons of using stlport v/s libstdc++ >with a gcc compiler 3.4 on FC2 (i.e. kernel 2.6.*)

there is no offical release of stlport that will compile with gcc3.4.x, the last released is 4.5.2 (ignoring the bad relase 4.6) and only works with 3.2.x (IIRC), if you want to use gcc 3.3 or 3.4 then you will need to get the cvs of stlport5 which is still in beta.

>portability issues? Which one is more portable (OS of interest: vxWorks, >netbsd, FC2)

we have used both stlport and more recently libstdc++ for a custom rtos, and in both cases you have to patch for your own thread/locking implentation, but both are similar.

>Essentially I need these details to determine if we will use STLport or >libstdc++

since you mentioned vxworks, i think you may be targeting an embedded platform, i would advise against using C++ at all. Now you may not have a choice, but c++/stl/exceptions/rtti all are all non-trival to get working.

regards,

Matthew J Fletcher
Serck Controls Ltd.


**********************************************************************
Serck Controls Ltd, Rowley Drive, Coventry, CV3 4FH, UK
Tel: +44 (0) 24 7630 5050   Fax: +44 (0) 24 7630 2437
Web: www.serck-controls.com  Admin: post@serck-controls.co.uk
A subsidiary of Serck Controls Pty. Ltd. Reg. in England No. 4353634
**********************************************************************
This email and files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the above. Any views or opinions presented are those of the author
and do not necessarily represent those of Serck Controls Ltd.


This message has been checked by MessageLabs
******************************************************************