In message <6daeedff54.ga...@wra1th.plus.com>
Gavin Wraith <ga...@wra1th.plus.com> wrote:
>ranlib liblua.a
>
>produced
>> gcc -std=gnu99 -o lua lua.o liblua.a -lm
>> gcc: error: liblua/a: No such file or directory
>> make: *** [lua] Error 1
>
>So, have I done something wrong, by omission or commission, or was the claim
>about filenaming in the help docs premature?
Just seen in the help docs:
Note we don't do suffix swapping for 'a' extensions.
That explains it. Sorry for the noise. Compilation now OK. I now need to
understand filepath conventions for shared libraries. Can I set things
up so that my application looks for its shared libraries in
MyApp:lib.so.<version>.
? Can I just compile the shared library as an ELF file and copy it there, or
does the
SOManager have to be brought into the picture? The libraries are not
in fact going to be shared at all - it is the runtime linking aspect,
not the sharing, that will be relevant.
--
Gavin Wraith (ga...@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
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
