| |
comp.sys.acorn.programmer |
In message <19f529b24d.phi...@philipnet.com> > Now, with the advent of the A9, it seems that RISC OS Developments have AIUI, Castle's distributed SCL cannot be loaded onto the A9, and it's Another more drastic, but perhaps ultimately more flexible solution, -- ----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
Philip Ludlam <nos...@philipnet.com> wrote:
> produced their own 32-bit version of the SharedCLibrary.
> If one was being particularly bitter one might assume that there's still
> a big dispute between ROD and Castle ;-) .
description.
> onto other ROD products (maybe even Select 4!) so I'm going to have to
> bite the bullet and ammend the RMEnsure and hope that 5.17 or earlier of
> the other SharedCLibrary isn't lurking around anywhere.
presume. Castle's SCL contains quite a number of extra functions that
ROL's doesn't. In practice, this means that any program linked with
Castle's stubs or indeed GCC's stubs will refuse to load at all on an A9
since ROL's SCL will not contain the extra chunks that refer to the
extra functions. Programs can of course be linked with StubsG, which
may or may not be practical.
designed to be loaded onto 26-bit systems. I don't know how practical
it would be (legalities aside) to load the SCL from RO5 ROM on the A9.
One solution would be for Castle to make their loadable SCL suitable for
the A9. I don't know what would be involved with this.
would be for developers to take the bull by its horns, and develop their
own open source SCL, starting by taking code from UnixLib. This would
level the playing field, and avoid inter-company politics. I believe
the amount of work involved would not be that large.
Peter Naulls - pe...@chocky.org | http://www.chocky.org/
--------------------------------------------------------------------------- -
RISC OS C Programming | http://www.riscos.info/c/
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----