In message <[EMAIL PROTECTED]>
Jan-Jaap van der Geer <[EMAIL PROTECTED]> wrote:
> Talking about libstdc++, I assume using the standard C++ classes
> (string, iostream, stl) means the resulting executable becomes
> dependent on SharedUnixLib? Looking at the info on riscos.info I
> could not find anything to suggest that this is the case.
>
> I did find references that it was possible to compile/link with
> -mlibscl, but apparently that did not mean that UnixLib is *not*
> used.
>
> In hindsight that seems reasonable, since SCL almost certainly does
> not know anything about these C++ classes, but it surprised me
> initially.
With GCCSDK 3.4.6 you can compile your C++ code with UnixLib or
SharedCLibrary as runtime library and the latter both for application
code and module code.
For GCCSDK 4.1.1, C++ code can only be compiled with UnixLib as runtime
library at the moment. I haven't found the time to try this with the
SharedCLibrary.
John.
--
John Tytgat, in his comfy chair at home BASS
[EMAIL PROTECTED] ARM powered, RISC OS driven
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
