OSLib 6.70 released

Erik Groenhuis e.groenhuis at xs4all.nl
Sun Aug 1 11:19:36 BST 2004


On 1 Aug 2004 David J. Ruck wrote:

> On 1 Aug 2004 Erik Groenhuis <e.groenhuis at xs4all.nl> wrote:
> 
> > On 30 Jul 2004 David J. Ruck wrote:
> > 
> > > On 8 Jul 2004 Tony van der Hoff <tony at mk-net.demon.co.uk> wrote:
> > > > Some 6 months after the last release, OSLib 6.70 is now available as a
> > > > binary download at http://ro-oslib.sourceforge.net/. The CVS tag is
> > > > oslib-670, for those who want the sources.
> > > 
> > > OSLibSupport library objects are junk. Please can we have a
> > > working version as a matter of urgency.
> > 
> > Moving from using the Toolbox with clib to using the Toolbox with
> > OSLibSupport is, indeed, not trivial.
> 
> [Snip]
>  
> > Hope this helps.
> 
> Thanks Erik, but the problem isn't moving to using OSLibSupport, but
> that the library objects provided in the 6.70 release are just ALF
> headers with no body, and wont work with anything.

I see what you mean. 112 bytes *is* a bit small for a library (8-).

For emergencies I recommend falling back to the 6.60 version of
OSLibSupport. The sources have not changed since last december.

In the meantime I have been trying to build OSLibSupport or even OSLib
from the CVS sources, but without any luck. It starts early with the
compilation of DefMod: (while compiling ....defmod.sources.c.cstrong)

'#include file "oslib/macros.h" wouldn't open'

and neither would oslib/os.h, oslib/osfile.h, oslib/territory.h, x.h,
lookup.h and trace.h.

In short: OSLib will not compile "out of the box".

As far as I can tell at the moment, the sources of OSLib will only
compile if there is an existing, compiled version of OSLib.
 
-- 
Erik Groenhuis http://www.xs4all.nl/~erikgrnh
Home of RCS for RISC OS v5.7.1.2  http://www.rcs.riscos.org.uk/
Csite on RiscPC with a StrongARM RISC processor and RISC OS 4.02



More information about the oslib-user mailing list