OSLib paths

[Tony van der Hoff]

On Sun, 26 Nov 2000, at 23:52:18, Tom Hughes <tom at compton.nu> wrote on
the subject "OSLib paths":

>I upgraded my main OSLib installation to 6.12 today and fell over
>all the path changes in a big way.
>
Argh! you can't turn your back for a second, without some-one cocking
things up ;-)

>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.
>
Yes, you're quite right, although no-one else seems to have noticed :-)

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

I believe the correct fix (which I'm using here) is to create another
OSLib directory at the same level as OSLib.o, and place the h and Hdr
directories inside that. 

Then change SetVars to :

-------------- next part --------------
A non-text attachment was scrubbed...
Name: SetVarsRO4,feb
Type: application/octet-stream
Size: 494 bytes
Desc: SetVarsRO4,feb
URL: <http://lists.compton.nu/pipermail/oslib-team/attachments/20001127/64f7d303/attachment.obj>
-------------- next part --------------

instead of the present rubbish. I would propose to do that for V6.20

>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?
>
Yes, it's a shame you weren't able to partake in the lengthy discussions
in oslib-user around the end of September on the subject. Many schemes
were proposed and rejected, and that was one of the subjects covered.

The prefix is necessary for the library using the 'deep' directory
structure. Naturally, I wanted to keep the source files identical
between the two versions, so the 'flat' library inherited it. I think
the participants to the discussion agreed it would not cause a problem,
given the appropriate paths.


-- 
Tony van der Hoff         |  mailto:OSLib at mk-net.demon.co.uk
Buckinghamshire, England  |  http://www.mk-net.demon.co.uk/oslib/
----------------------------------------------------------------