Ron wrote:
The !SharedLibs ReadMe is very helpful for a newcomer to understand
it's purpose.
That's good to know :-)
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.
I think this is a case of the documentation lagging behind development.
When I first wrote the !ReadMe, the name translation for the dynamic
loader was very basic. At some point it was upgraded to use the
riscosify code to make using libraries created with the autobuilder easier.
For linking you can just use -lefg, and avoid the need to
get around gcc treating libefg/so as a directory.
Well, -lefg is the preferred way of doing it.
Actually simply renaming to libefg for -I would work, but it is
simpler to just use SharedLib: and avoid the translations
altogether.
I'm not sure what you mean here, -I is used for include directories.
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)
Perhaps it's time I looked at writing or porting some version of
ldconfig to generate the symlink files automatically.
Anyway, I'll fix the documentation so that it recommends the use of Unix
style names.
Thanks for the feed back,
Lee.
_______________________________________________
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
