OSLib and ELF

[Tony van der Hoff]

On 12 Apr at 9:47 "David J. Ruck" <druck at druck.org.uk> wrote in message
<gemini.jgdn2t02wtq8l01s4.druck at druck.org.uk>

> John Tytgat <John.Tytgat at aaug.net> wrote:
> > But then we're talking about developers updating APCS-R programs which
> > do not run on Iyonix nor A9home ? I would be very amazed to hear
> > examples of this.
> 
> There are Risc PC's being used in industrial control applications, due to
> the expense of qualifying the hardware they wont be replaced with Iyonix
> or A9s, but it will go over to competitors x86 boxes when the spares run
> out.
> 
True, I used to write industrial control applications on RISC-PCs (and
A310s, and A3000s :), but those have all long been consigned to the
scrap-bin in favour of Linux. Frankly I would no longer touch RISC OS with a
barge-pole for such applications.

So, whatever we do with OSLib won't retain or get those users back...

> > Moreover, I don't see any reason why they would upgrade OSLib library ?
> > For new APIs ? Would be odd seen that new APIs are targetting the OS
> > versions of RO5/Select. Bug fixes ? I think we have a very modest bug
> > fix set made the last years.
> 
> True, but the occational incorrect flag is noticed, and if the sources
> can't be rebuilt natively the library can't be used. But look on the
> bright side, support contracts are only 15 years, so early in the next
> decade every RISC OS machine will have been replaced anyway, so it wont
> matter anymore.

OK, but if we create a 6.9 branch, then we can do bug-fixes as much as we
like on that, and retain native builds on it. Seems a reasonable compromise
to me.


-- 
Tony van der Hoff        | mailto:tony at vanderhoff.org
Buckinghamshire, England