OSLib paths

[Tom Hughes]

I upgraded my main OSLib installation to 6.12 today and fell over
all the path changes in a big way.

The current !ReadMe (at least in the RO4 version) claims that so
long as I continue to use OSLibInclude: everything will work, but
it doesn't because the SetVars shipped with it sets OSLibInclude$Path
to be the same as OSLib$Path, so I would still need the "oslib/" on
all my includes.

Even after I fixed that I had to change my link commands to link
against OSLib:OSLib.o.OSLib instead of OSLib:o.OSLib.

In addition to all this, the header files all seem to have been
changes to put an "oslib/" prefix in when including other header
files. Surely this is not needed as the C standard says that when
one header includes another the current directory is always the
first place that is searched?

Tom

-- 
Tom Hughes (tom at compton.nu)
http://www.compton.nu/
...Psychoceramics: The study of crackpots.