The !SharedLibs ReadMe is very helpful for a newcomer to understand it's purpose. However I found the paragraph explaining how to use the -soname= option completely wrong. If "/" is used, the lib will not load for either use by gcc at linking, or for the executable that is linked to it. You must use, -soname=libefg.so [.so.1.2] syntax.
For linking you can just use -lefg, and avoid the need to get around gcc treating libefg/so as a directory. Actually simply renaming to libefg for -I would work, but it is simpler to just use SharedLib: and avoid the translations altogether. The next step will be to write the shared object (libefg/so) and any links directly to SharedLib:lib/ instead of producing it in the CSD. (untried) >From the point of view of GCC, everything is in . files. with no deviation. "/" is a directory I haven't found the reason, wether unixlib or GCC, but when there is a gcc command error, it reports back with "/" instead of "." in the supposed file causing the error. It's not a show stopper, but it would be better if it kept to the same theme, I think. Ron M. _______________________________________________ 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
