In message <49317ff0.60...@sky.com>
Lee Noar wrote:
> You're not doing anything wrong, as such, it's just unfortunate that
> riscosify() doesn't handle library filenames very well, perhaps because
> it has what might be seen as multiple suffixes. The easiest way around
> it is to use
> On Mon, 1 Dec 2008 21:59:01 +0200 John Tytgat wrote:
>
>> Thanks Lee this seemed to get it working. It did lead to the problem
>> with the library being created in the root rather than the development
>> directory but I got round that by using @/libhello.so.0.0.
>
> Does ./libhello.so.0.0 equa
> On Sat, 29 Nov 2008 17:46:24 Lee Noar wrote:
>
> alan buckley wrote:
>> I don't seem to be able to create shared libraries
>> on RISC OS.
>>
>> I found a simple example on the web and tried the
>> following to build it in an Obey file:
>>
>> gcc -fPIC -Wall -g -c libhello.c
>> gcc -shared -Wl
In message <[EMAIL PROTECTED]>
alan buckley <[EMAIL PROTECTED]> wrote:
> Thanks Lee this seemed to get it working. It did lead to the problem
> with the library being created in the root rather than the development
> directory but I got round that by using @/libhello.so.0.0.
Does ./libh
alan buckley wrote:
I don't seem to be able to create shared libraries
on RISC OS.
I found a simple example on the web and tried the
following to build it in an Obey file:
gcc -fPIC -Wall -g -c libhello.c
gcc -shared -Wl,-soname,libhello.so.0 -olibhello/so/0/0 libhello.o
The Result I got
I don't seem to be able to create shared libraries
on RISC OS.
I found a simple example on the web and tried the
following to build it in an Obey file:
gcc -fPIC -Wall -g -c libhello.c
gcc -shared -Wl,-soname,libhello.so.0 -olibhello/so/0/0 libhello.o
The Result I got was:
/ADFS::HardDisc4.
